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

91–100 of 280 posts

Re: Claude Advanced Tool Use

#91

Post by 867-5309 »

eli wrote: post #75
johnfn wrote: post #70

Earlier quoted context omitted.

Really? Hmm... where in the HTTP spec does it allow for returning an arbitrary subset of any specific request, rather than the whole thing? And where does it ensure all the results are keyed by id so that you can actually build and update a sensible cache around all of it rather than the mess that totally free-form HTTP responses lead to? Oh weird HTTP doesn't have any of that stuff? Maybe we should make a new spec,…

An HTTP Range request asks the server to send parts of a resource back to a client. Range requests are useful for various clients, including media players that support random access, data tools that require only part of a large file, and download managers that let users pause and resume a download. https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Ran...

also handy for bypassing bandwidth restrictions: capped at 100kbps? launch 1000 workers to grab chunks then assemble the survivors

Re: Claude Advanced Tool Use

#92

Post by bravura »

_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…

Isn't the challenge that introspecting graphql will lead to either a) a very long set of definitions consuming many tokens or b) many calls to drill into the introspection?

Re: Claude Advanced Tool Use

#93

Post by abraxas »

tfirst wrote: post #2

We seem to be on a cycle of complexity -> simplicity -> complexity with AI agent design. First we had agents like Manus or Devin that had massive scaffolding around them, then we had simple LLMs in loops, then MCP added capabilities at the cost of context consumption, then in the last month everything has been bash + filesystem, and now we're back to creating more complex tools. I wonder if there will be another roun…

Yeah, seems like the agent industry is spinning wheels a bit. As that old adage goes, when there are a hundred treatments you can be sure there is no cure.

Re: Claude Advanced Tool Use

#95

Post by mattmanser »

wrs wrote: post #59
awesome_dude wrote: post #50

Earlier quoted context omitted.

Without wishing to take part in a pile on - I am wondering why you're using graphql if you are kneecapping it and restricting it to set queries.

Because it solves all sorts of other problems, like having a well-defined way to specify the schema of queries and results, and lots of tools built around that. I would be surprised to see many (or any) GQL endpoints in systems with significant complexity and scale that allow completely arbitrary requests.

OpenAPI does the same thing for http requests, with tooling around it.

With typed languages you can auto-generate OpenAPI schemas from your code.

Re: Claude Advanced Tool Use

#96

Post by cadamsdotcom »

Very clever. Tool search and “code that can orchestrate tool calls” are features that make utter sense and should become opt out for all tools - not opt in.

How did the industry not think to do this in the first place :)

Re: Claude Advanced Tool Use

#97

Post by IgorPartola »

_ea1k wrote: post #54
jameslk wrote: post #13

> Tool Search Tool, which allows Claude to use search tools to access thousands of tools without consuming its context window At some point, you run into the problem of having many tools that can accomplish the same task. Then you need a tool search engine, which helps you find the most relevant tool for your search keywords. But tool makers start to abuse Tool Engine Optimization (TEO) techniques to push their tools…

We just need another tool for ranking tools via ToolRank. We'll crowdsource the ranking from a combination of user responses to the agents themselves as well as a council of LLM tool rankers.

PageRank was named after Larry Page and not because it ranked pages. So to follow the pattern, you must first find someone whose last name is Tool.

Re: Claude Advanced Tool Use

#98

Post by ibash »

steveklabnik wrote: post #73
refibrillator wrote: post #71

Earlier quoted context omitted.

> It works better! > I strongly believe it is one of the best technologies for AI agents Do you have any quantitative evidence to support this? Sincere question. I feel it would add some much needed credibility in a space where many folks are abusing the hype wave and low key shilling their products with vibes instead of rigor.

I have thought about this for all of thirty seconds, but it wouldn't shock me if this was the case. The intuition here is about types, and the ability to introspect them. Agents really love automated guardrails. It makes sense to me that this would work better than RESTish stuff, even with OpenAPI.

Better than rest is a low bar though. Ultimately agents should rarely be calling raw rest and graphql apis, which are meant for programmatic use.

Agents should be calling one level of abstraction higher.

Eg calling a function to “find me relevant events in this city according to this users preferences” instead of “list all events in this city”.

Re: Claude Advanced Tool Use

#100

Post by ra »

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.

Post reply on HN