Get a tool by ID
Returns a single tool in the unified `Tool` shape, whatever its type.
The contract the model sees (`name`, `description`, `inputs`,
`outputs`) and the controls that gate it (`enabled`, `direct_use`,
`availability`) sit at the top level; everything specific to how the
tool runs is nested under the key matching `type`.
`Authorization` headers are stripped from `api.request.headers`; other
header values pass through with variable references translated to the
`{var:<name>|<default>}` form.
Authentication
AuthorizationBearer
Bearer authentication of the form Bearer <token>, where token is your auth token.
Path parameters
tool_id
The tool's id
Response
The tool
id
The tool's id
type
Which kind of tool this is, and which implementation key is present
name
The tool's name, as the model sees it
description
What the tool does, as the model sees it
inputs
The inputs the tool declares
outputs
The values the tool returns.
enabled
Whether the tool is available to the Agent at all
direct_use
Whether the Agent may call this tool on its own, rather than only as a step inside a process.
availability
The rule that gates when the tool is offered. null when the tool is always available.
api
How an api tool calls its HTTP endpoint
code
The sandboxed Python a code tool runs
Errors
400
Bad Request Error
401
Unauthorized Error
403
Forbidden Error
404
Not Found Error
429
Too Many Requests Error
500
Internal Server Error