Custom tools
Register an HTTP endpoint the reasoning agent can call in your project, such as an internal pricing service or a vendor API.
Sometimes an answer needs something that isn't in your data: a price from an internal service, a figure from a vendor API. Custom tools let you register an endpoint so the agent can call it while it answers.
Where to find it
Open Settings › Tools, or go to /settings/tools. Tools belong to the current project; switching projects switches the list.
The page, Project tools, reads: "Add MCP servers or HTTP endpoints the agent can call. Used for creative concept generation, external trend lookups, custom analytics endpoints, anything that's not in the warehouse." A counter shows N registered · M enabled.
Tool kinds
| Kind | What happens when the agent calls it |
|---|---|
| HTTP endpoint | Tattva sends a request to your endpoint and passes the response to the agent. Use this kind. |
| MCP server | The tool is registered and the agent can see it, but calls return an error: this build doesn't run MCP tools. |
The form labels MCP as recommended. Choose HTTP endpoint if you need the tool to work.
Adding an HTTP tool
- Click + Add tool.
- Fill in:
- Name, for example "Pricing lookup".
- Slug: filled in from the name if you leave it blank.
- Kind: HTTP endpoint.
- Description: what the tool does, in a sentence. The agent reads it to decide when to call the tool, so be specific.
- HTTP endpoint: the URL to call.
- Auth header (optional), for example
Bearer ….
- Click Register. The tool is enabled straight away.
What your endpoint receives
A POST with a JSON body. The agent's input sits under input:
{ "input": { "sku": "SKU-A", "region": "north" } }Return JSON or text. The agent sees the status code and the first 8,000 characters of the response.
Managing tools
Each row shows the name, slug, kind, enabled or disabled, and the endpoint.
- Disable keeps the tool but stops the agent calling it. Enable turns it back on.
- Remove unregisters it after you confirm Remove this tool?.
Security
- The agent sends only the input it composed for the tool, not the rest of your project.
- Any signed-in member of the project can register or remove a tool. Review the list now and then; a tool someone added stays active until it's disabled or removed.
- Don't expose your warehouse through a custom tool. Connect it on the Sources page instead, where Tattva's query limits and personal-data rules apply.