Tool Sets
Manage tool sets and the tools they contain. Tool sets group related tools, and tools define specific capabilities available to agents.
When a tool set is managed, only API key actors can modify its tools; human (profile) actors cannot.
List tool sets
Create a new tool set
Get a tool set by ID
Update a tool set
Delete a tool set
Get consumed OpenAPI spec
List tool set events
ModelsExpand Collapse
ApprovalRequirementFilter { always, only }
Approval filters that will automatically set the approval requirement on tools synced from an external source
ToolSet { metadata, spec, info }
Standard metadata for persistent, named resources (e.g., agents, tools, prompts)
name: string
Human-readable name for the resource (e.g., “Customer Support Agent”, “Email Tool”) Required for resources that users interact with directly
Approval filters that will automatically set the approval requirement on tools synced from an external source
baseUrl?: string
Base URL for dispatching tool calls. If set, overrides the server resolved from the spec’s servers array.
headers?: Record<string, string>
Headers sent when fetching the spec from a URL and when dispatching tool calls.
serverName?: string
Name of the server entry in the spec’s servers array (OpenAPI 3.2 server.name field). Used to select which server URL to dispatch to when base_url is not set. If unset, the first server is used. Ignored when base_url is set.
Approval filters that will automatically set the approval requirement on tools synced from an external source
Tool set information
A profile identifies a user or non-human principal (such as an API key) at the account level. Profiles are account-scoped and can be granted access to multiple workspaces.
ToolSetAdapter { http, mcp, openapi }
Approval filters that will automatically set the approval requirement on tools synced from an external source
baseUrl?: string
Base URL for dispatching tool calls. If set, overrides the server resolved from the spec’s servers array.
headers?: Record<string, string>
Headers sent when fetching the spec from a URL and when dispatching tool calls.
serverName?: string
Name of the server entry in the spec’s servers array (OpenAPI 3.2 server.name field). Used to select which server URL to dispatch to when base_url is not set. If unset, the first server is used. Ignored when base_url is set.
Approval filters that will automatically set the approval requirement on tools synced from an external source
ToolSetAdapterMcp { excludeTools, headers, includeTools, 2 more }
Approval filters that will automatically set the approval requirement on tools synced from an external source
ToolSetAdapterOpenAPI { baseUrl, excludeTools, headers, 5 more }
baseUrl?: string
Base URL for dispatching tool calls. If set, overrides the server resolved from the spec’s servers array.
headers?: Record<string, string>
Headers sent when fetching the spec from a URL and when dispatching tool calls.
serverName?: string
Name of the server entry in the spec’s servers array (OpenAPI 3.2 server.name field). Used to select which server URL to dispatch to when base_url is not set. If unset, the first server is used. Ignored when base_url is set.
Approval filters that will automatically set the approval requirement on tools synced from an external source
ToolSetEvent { metadata, event, info, toolSetId }
A single event in the tool set’s operation timeline.
info?: Info { createdBy, toolSet }
A profile identifies a user or non-human principal (such as an API key) at the account level. Profiles are account-scoped and can be granted access to multiple workspaces.
Standard metadata for persistent, named resources (e.g., agents, tools, prompts)
name: string
Human-readable name for the resource (e.g., “Customer Support Agent”, “Email Tool”) Required for resources that users interact with directly
ToolSetInfo { agentCount, createdBy, lastSync, toolCount }
A profile identifies a user or non-human principal (such as an API key) at the account level. Profiles are account-scoped and can be granted access to multiple workspaces.
ToolSetSpec { adapter, description }
Approval filters that will automatically set the approval requirement on tools synced from an external source
baseUrl?: string
Base URL for dispatching tool calls. If set, overrides the server resolved from the spec’s servers array.
headers?: Record<string, string>
Headers sent when fetching the spec from a URL and when dispatching tool calls.
serverName?: string
Name of the server entry in the spec’s servers array (OpenAPI 3.2 server.name field). Used to select which server URL to dispatch to when base_url is not set. If unset, the first server is used. Ignored when base_url is set.
Approval filters that will automatically set the approval requirement on tools synced from an external source
Tool SetsTools
Manage tool sets and the tools they contain. Tool sets group related tools, and tools define specific capabilities available to agents.
When a tool set is managed, only API key actors can modify its tools; human (profile) actors cannot.
List tools
Create a new tool
Get a tool by ID
Update a tool
Delete a tool
ModelsExpand Collapse
Tool { metadata, spec, info }
Standard metadata for persistent, named resources (e.g., agents, tools, prompts)
name: string
Human-readable name for the resource (e.g., “Customer Support Agent”, “Email Tool”) Required for resources that users interact with directly
A profile identifies a user or non-human principal (such as an API key) at the account level. Profiles are account-scoped and can be granted access to multiple workspaces.
Standard metadata for persistent, named resources (e.g., agents, tools, prompts)
name: string
Human-readable name for the resource (e.g., “Customer Support Agent”, “Email Tool”) Required for resources that users interact with directly
ToolInfo { createdBy, toolSet }
A profile identifies a user or non-human principal (such as an API key) at the account level. Profiles are account-scoped and can be granted access to multiple workspaces.
Standard metadata for persistent, named resources (e.g., agents, tools, prompts)
name: string
Human-readable name for the resource (e.g., “Customer Support Agent”, “Email Tool”) Required for resources that users interact with directly