Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Claude Advanced Tool Use

anthropic.com

Post reply on HN
Print view View original

181–190 of 280 posts

Re: Claude Advanced Tool Use

#181

Post by lukan »

jawns wrote: post #77

I'm starting to notice a pattern with these AI assistants. Scenario: I realize that the recommended way to do something with the available tools is inefficient, so I implement it myself in a much more efficient way. Then, 2-3 months later, new tools come out to make all my work moot. I guess it's the price of living on the cutting edge.

The frustrating part is, with all the hype it is hard to see, what are really the working ways right now. I refused to go your way to live on the edge and just occasionally used ChatGPT for specific tasks, but I do like the idea to get AI assistants for the old codebases and gave the modern ways a shot just now again, but it still seems messy and I never know if I am simply not doing it right, or if there simply is no right way and sometimes things work and sometimes they don't. I guess I wait some more time, before also invest in building tools, that will be obsolete in some weeks or months.

Re: Claude Advanced Tool Use

#182

Post by slhck »

esperent wrote: post #161
falcor84 wrote: post #134

Earlier quoted context omitted.

That's exactly what Claude Skills do [0], and while this tool search appears to be distinct, I do think that they're on the way to integrating MCP and Skills. [0] https://code.claude.com/docs/en/skills

I haven't had much luck with skills being called appropriately. When I have a skill called "X doer", and then I write a prompt like "Open and do X", it almost never loads up the skill. I have to rewrite the prompt as "Open and do X using the X doer skill". Which is basically exactly as much effort as what I was doing previously of having prewritten sub-prompts/agents in files and loading up the file each time I want…

Same experience here – it seems I have to specifically tell it to use the "X skill" to trigger it reliably. I guess with all the different rules set up for Claude to follow, it needs that particular word to draw its attention to the required skill.

Re: Claude Advanced Tool Use

#184

Post by aryehof »

This seems to derive from the “skills” feature. A set of “meta tools” that supports granular discovery of tools, but whereas you write (optional) skills code yourself, a second meta tool can do it for you in conjunction with (optional) examples you can provide.

Am I missing something else?

Re: Claude Advanced Tool Use

#185

Post by [deleted] »

_pdp_ wrote: post #24

Our agentic builder has a single tool. It is called graphql. The agent writes a query and executes it. If the agent does not know how to do particular type of query then it can use graphql introspection. The agent only receives the minimal amount of data as per the graphql query saving valuable tokens. It works better! Not only we don't need to load 50+ tools (our entire SDK) but it also solves the N+1 problem when u…

[deleted]

Re: Claude Advanced Tool Use

#187

Post by sibeliuss »

_pdp_ wrote: post #24

Our agentic builder has a single tool. It is called graphql. The agent writes a query and executes it. If the agent does not know how to do particular type of query then it can use graphql introspection. The agent only receives the minimal amount of data as per the graphql query saving valuable tokens. It works better! Not only we don't need to load 50+ tools (our entire SDK) but it also solves the N+1 problem when u…

GraphQL FTW

Re: Claude Advanced Tool Use

#189

Post by jbs789 »

Culonavirus wrote: post #175
ra wrote: post #100

This is heading in the wrong direction. > The future of AI agents is one where models work seamlessly across hundreds or thousands of tools. Says who? I see it going the other way - less tools, better skills to apply those tools. To take it to an extreme, you could get by with ShellTool.

> less tools, better skills to apply those tools All models have peaked (the velocity of progress is basically zero compared to previous years) -there are not going to be "better skills" (any time soon). All these bubbled up corps(es) have to try to sell what they can, agent this, tool that, buzzword soup to keep the investors clueless one more year.

That’s one narrative.

It’s typical for the foundation to settle before building on top of it.

Additionally do agree there is immense commercial pressure.

I’m quite curious how it all shakes out across the majors. If the foundation is relatively similar then the differentiator (and what they can charge) will determine their returns on this investment.

As a user, I love the competition and the evolution.

As an investor, am curious how it shakes out.

Re: Claude Advanced Tool Use

#190

Post by dalemhurley »

FridgeSeal wrote: post #141
fny wrote: post #74

Earlier quoted context omitted.

Why exactly do we need a new language? The agents I write get access to a subset of the Python SDK (i.e. non-destructive), packages, and custom functions. All this ceremony around tools and pseudo-RPC seems pointless given LLMs are extremely capable of assembling code by themselves.

Woah woah woah, you’re ignoring a whole revenue stream caused by deliberately complicating the ecosystem, and then selling tools and consulting to “make it simpler”! Think of all the new yachts our mega-rich tech-bros could have by doing this!

Tool search is formalising what a lot of teams have been working towards. I had previously called it tool caller, the LLM knew there was tools for domains and then when the domain was mentioned, the tools for the domain would be loaded, this looks a bit smarter.
Post reply on HN