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
type ApprovalRequirementFilter struct{…}
Approval filters that will automatically set the approval requirement on tools synced from an external source
type ToolSet struct{…}
Metadata ResourceMetadata
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
Spec ToolSetSpec
Approval filters that will automatically set the approval requirement on tools synced from an external source
BaseURL stringOptional
Base URL for dispatching tool calls. If set, overrides the server resolved from the spec’s servers array.
Headers map[string, string]Optional
Headers sent when fetching the spec from a URL and when dispatching tool calls.
ServerName stringOptional
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.
Metadata AccountResourceMetadata
Spec ProfileSpec
type ToolSetAdapter struct{…}
Approval filters that will automatically set the approval requirement on tools synced from an external source
BaseURL stringOptional
Base URL for dispatching tool calls. If set, overrides the server resolved from the spec’s servers array.
Headers map[string, string]Optional
Headers sent when fetching the spec from a URL and when dispatching tool calls.
ServerName stringOptional
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
type ToolSetAdapterMcp struct{…}
Approval filters that will automatically set the approval requirement on tools synced from an external source
type ToolSetAdapterOpenAPI struct{…}
BaseURL stringOptional
Base URL for dispatching tool calls. If set, overrides the server resolved from the spec’s servers array.
Headers map[string, string]Optional
Headers sent when fetching the spec from a URL and when dispatching tool calls.
ServerName stringOptional
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
type ToolSetEvent struct{…}
A single event in the tool set’s operation timeline.
Metadata OperationMetadata
Metadata for ephemeral operations and activities (e.g., objectives, executions, runs)
Info ToolSetEventInfoOptional
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.
Metadata AccountResourceMetadata
Spec ProfileSpec
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
type ToolSetInfo struct{…}
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.
Metadata AccountResourceMetadata
Spec ProfileSpec
type ToolSetSpec struct{…}
Approval filters that will automatically set the approval requirement on tools synced from an external source
BaseURL stringOptional
Base URL for dispatching tool calls. If set, overrides the server resolved from the spec’s servers array.
Headers map[string, string]Optional
Headers sent when fetching the spec from a URL and when dispatching tool calls.
ServerName stringOptional
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
type Tool struct{…}
Metadata ResourceMetadata
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
Spec ToolSpec
Config ToolSpecConfig
Config defines the adapter to use for the tool. This is used to determine how the tool is called. For example, if the tool is an HTTP tool, the adapter will be Http. If the tool is an inline tool, the adapter will be Inline.
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.
Metadata AccountResourceMetadata
Spec ProfileSpec
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
type ToolInfo struct{…}
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.
Metadata AccountResourceMetadata
Spec ProfileSpec
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
type ToolSpec struct{…}
Config ToolSpecConfig
Config defines the adapter to use for the tool. This is used to determine how the tool is called. For example, if the tool is an HTTP tool, the adapter will be Http. If the tool is an inline tool, the adapter will be Inline.
type ToolSpecConfig struct{…}
Config defines the adapter to use for the tool. This is used to determine how the tool is called. For example, if the tool is an HTTP tool, the adapter will be Http. If the tool is an inline tool, the adapter will be Inline.