Manual tools

When to use a manual tool

Reach for a manual tool when you need a single, specific HTTP call and don't need (or want) the Toolkit Builder to research and draft a whole set. From the Tools tab, click Add a tool.

Fields

• Function name — how the tool is identified to the model.
• Method — GET, POST, PUT, PATCH, or DELETE.
• Description — tells the model when to use this tool; be specific about what it does and when it's appropriate.
• URL template — the endpoint, with {param} placeholders for values the model fills in (e.g. https://api.example.com/orders/{order_id}).
• Headers — JSON, including any authentication headers. Reference stored credentials with {{secret.your_alias}} rather than pasting a raw key — see Connecting credentials.
• Body template — JSON, for POST/PUT/PATCH requests, also supporting {param} placeholders.
• Parameters — a JSON Schema describing the arguments the model can supply, which the platform validates before calling your endpoint.

Generate with AI

If you'd rather not hand-write the definition, use Generate with AI: describe the tool in plain English and Claude drafts the method, URL, headers, body, and parameter schema from the live API docs.

Testing before you save

The Test dialog runs the tool (draft or saved) against the real endpoint without saving anything, so you can confirm it works — and see the actual request and response — before it's available to the agent.

Editing an existing tool

Open a saved tool to Enable/Disable it, Revert unsaved changes, Save changes, or Delete it. Disabling is non-destructive and a good way to temporarily take a tool out of rotation without losing its configuration.