Get a tool
One tool’s full definition: its parameters, its approval flag, and the name the model sees.
What a tool holds
spec carries all five fields a tool is created with:
state is STATE_AVAILABLE or STATE_OMITTED. An omitted tool reads back fine here; it is hidden from agents, not from you.
info.signature keys the tool
info holds createdBy and a signature, a hash of the tool’s definition. A synced tool set enforces uniqueness on (tool_set_id, signature), so the signature is what makes a re-sync idempotent: an unchanged tool keeps its signature and is not duplicated.
External ID
Tools take an external ID scoped to their tool set, so pass thetool_... value or the external_id: form. A missing ID is a 404. Synced tools (MCP, OpenAPI) come in without one unless you set it; a hand-defined HTTP or bare tool is where you usually pick your own.
Related
List tools
Omit a tool
STATE_OMITTED.Create a tool set
Approve a tool call
requiresApproval triggers.Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Workspace ID.
"workspace_01HXKD2E5NQM3T9AYWCF133E3Q"
Tool set ID. Accepts the canonical ts_… form or the external_id: form.
"toolset_01HXKD2E5NQM3T9AYWCFNRMN74"
Tool ID. Accepts the canonical tool_… form or the external_id: form.
"tool_01HXKD2E5NQM3T9AYWCFWVYY9K"
Response
OK
Standard metadata for persistent, named resources (e.g., agents, tools, prompts)
The current lifecycle state of the tool. Output only. Use the :omit and :restore actions to transition; tool set syncs may also update it.
STATE_UNSPECIFIED, STATE_AVAILABLE, STATE_OMITTED, STATE_ARCHIVED