Tool catalog

One short list on every request

Every tool a model can call costs tokens on every request: its name, its description and its parameters. With 299 native tools and your connected servers, sending all of them every time would pay for a long menu on every turn and blur the model's choice.

So every request carries one fixed list: 26 everyday tools plus three bridges that reach the rest. The list never changes with the ask, which keeps the request steady and cheap to cache. It grows only by the tools you pinned, the send tools on a Discord or Telegram turn, and deep research while its chip is on.

The three bridges

• tool_search: searches every tool you are allowed to use, native and MCP alike, by what it does ("calendar event", "zip folder"). Words in a tool's name count most.
• tool_describe: returns one tool's full parameters, so the call is written against the real shape.
• tool_call: runs any tool by name, through the same dispatcher as a direct call.

The catalog behind them is rebuilt from the live tool list on every request, so a server's tools are there the moment it connects.

The same rules for every tool

tool_call grants nothing a direct call would not. It goes through the same dispatcher, the same rails, the same permission level and the same record, and the record shows the real tool's name, never a wall of tool_call. The bridges cannot call themselves, and arguments that are not valid JSON are sent back to be fixed, never run.

Where the whole catalog rides

The Forge and Swarm modes carry the whole catalog on every request, because a long build is where an extra round trip to find a tool costs the most. Spark carries its own short list for chat. Helpers carry a wider set with the repository tools. On Anthropic models that support it, the provider's own tool search does the finding.

Pinning, and the switch

• Pin a tool on the Tools page (up to 12) and it rides on every request, ahead of the rest.
• Smart tool catalog, under Tool settings on the same page, is on. Turn it off to send every tool on every request.

The full list, with the descriptions the model reads, is the Tool reference.