/agent-management | Type: Embedded | PCID required: No
Tools
| Tool | Description |
|---|---|
agent_create | Create a new agent with specified configuration including name, description, instructions, tools, and resources. Two ways to add server tools: (1) Add all tools from a server: {“name”: “github”, “allTools”: true} — no need to list individual tools. (2) Add specific tools: call capabilities_discover to find relevant servers/tools, then list them in the tools field. Returns the created agent with its ID. |
agent_update | Update an existing agent. Only provided fields will be updated - other fields remain unchanged. Requires the agent ID from create or read operations. Two ways to add server tools: (1) All tools from a server: {“name”: “github”, “allTools”: true}. (2) Specific tools: call capabilities_discover to find relevant servers/tools, then list them. Example: If user says “add all github tools”, use {“name”: “github”, “allTools”: true}. |
agent_read | Get detailed information about an agent including its configuration, tools, resources, and permissions. Use this to inspect an agent before updating it or to understand its capabilities. |
agent_invoke | Invoke an agent and get its response. Use this to leverage agent capabilities for data processing, decision making, or complex tasks. The agent can be invoked with a message and optionally continue a conversation using chatId. Returns the agent’s response, chatId for continuing conversations, and agentId. |
agent_list | List all agents accessible to the current user. Returns a summary of each agent including its ID, name, and description. Use this to discover available agents before invoking or updating them. |
chat_create | Create a new chat session for an agent. A chat provides a persistent conversation context that maintains message history across multiple agent_invoke calls. After creating a chat, use agent_invoke with the returned chatId to send messages within this conversation. |
chat_list | List all chat sessions for a specific agent. Returns chat metadata including ID, name, agent association, and creation date. Use this to find existing conversations to resume via agent_invoke. |
chat_reset_conversation | Reset a chat’s conversation history, clearing all messages. The chat itself is preserved but its message history is wiped clean. Use this to start a fresh conversation within an existing chat session. The next agent_invoke call with this chatId will behave as if the conversation just started. |
chat_list_artifacts | List all artifacts associated with a chat. Returns artifact metadata including IDs, names, MIME types, sizes, and download URLs. Artifacts are created by agents during code execution (via createArtifact) or uploaded by users. |
agent_publish_release | Publish a release for an agent, locking in its current configuration as a versioned snapshot. A release is required before an agent can be made available as a public template. If nothing has changed since the last release, returns a message indicating nothing to release. |
agent_toggle_public_template | Toggle whether an agent is available as a public template in the template gallery. When enabling (available=true), the agent must have at least one published release. Provide a category and optional tags. When disabling (available=false), the agent is removed from the public gallery. Use agent_publish_release first to create a release before enabling. |
agent_create
Create a new agent with specified configuration including name, description, instructions, tools, and resources. Two ways to add server tools: (1) Add all tools from a server: {“name”: “github”, “allTools”: true} — no need to list individual tools. (2) Add specific tools: call capabilities_discover to find relevant servers/tools, then list them in the tools field. Returns the created agent with its ID. Parameters:| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
name | string | Yes | — | Display name for the agent |
description | string | Yes | — | Description of what the agent does |
instructions | string | Yes | — | System instructions/prompt for the agent - guides the agent behavior and capabilities |
outputSchema | string | No | — | Optional JSON schema for agent output structure |
promptExamples | string[] | No | [] | Example prompts shown as suggestion bubbles in the chat UI. These help users understand what the agent can do. Example: [“Analyze this RFP”, “Draft a response for this opportunity”] |
selectedModel | string | No | — | LLM model for the agent. If omitted, defaults to sonnet. |
introMessage | string | No | — | Welcome message shown when a user opens the agent chat for the first time. |
servers | any | No | [] | MCP servers and tools to grant the agent access to. Two options per server: (1) All tools: {“name”: “github”, “allTools”: true} — includes every tool from the server. (2) Specific tools: {“name”: “google-drive”, “tools”: {“google-drive_list_files”: {}}} — call capabilities_discover to find relevant servers/tools first. Examples: [{“name”: “github”, “allTools”: true}, {“name”: “slack”, “tools”: {“slack_send_message”: {}}}]. For agents without any tool access, use empty array: [] |
resources | any[] | No | [] | Generic resources configuration (advanced use) |
datastores | object[] | No | [] | NOT YET SUPPORTED. Granting datastore access during agent creation is not yet implemented. Do NOT use this field - inform the user this feature is coming soon. |
filestores | object[] | No | [] | NOT YET SUPPORTED. Granting filestore access during agent creation is not yet implemented. Do NOT use this field - inform the user this feature is coming soon. |
knowledgeBases | object[] | No | [] | NOT YET SUPPORTED. Granting knowledge base access during agent creation is not yet implemented. Do NOT use this field - inform the user this feature is coming soon. |
workflows | object[] | No | [] | Workflows the agent can trigger |
bindToWorkflow | object | No | — | Optionally bind this agent to a workflow immediately after creation. Agent will be available as a resource in the workflow for calling via config.callAgent(config.getAgent(“resourceName”)) |
agent_update
Update an existing agent. Only provided fields will be updated - other fields remain unchanged. Requires the agent ID from create or read operations. Two ways to add server tools: (1) All tools from a server: {“name”: “github”, “allTools”: true}. (2) Specific tools: call capabilities_discover to find relevant servers/tools, then list them. Example: If user says “add all github tools”, use {“name”: “github”, “allTools”: true}. Parameters:| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
agentId | string | Yes | — | ID of the agent to update (e.g. “ua_abc123”) |
name | string | No | — | Updated display name for the agent |
description | string | No | — | Updated description of what the agent does |
instructions | string | No | — | Updated system instructions/prompt for the agent |
outputSchema | string | No | — | Updated JSON schema for agent output structure |
promptExamples | string[] | No | — | Updated example prompts shown as suggestion bubbles in the chat UI. |
selectedModel | string | No | — | Updated LLM model for the agent. |
introMessage | string | No | — | Updated welcome message shown when a user opens the agent chat. |
servers | any | No | — | Updated MCP servers and tools configuration. If provided, replaces existing servers completely. Use {“name”: “server”, “allTools”: true} to add all tools from a server, or call capabilities_discover to find specific tools. Example: [{“name”: “github”, “allTools”: true}, {“name”: “slack”, “tools”: {“slack_send_message”: {}}}] |
resources | any[] | No | — | Updated generic resources configuration |
datastores | object[] | No | — | NOT YET SUPPORTED. Granting datastore access is not yet implemented. Do NOT use this field - inform the user this feature is coming soon. |
filestores | object[] | No | — | NOT YET SUPPORTED. Granting filestore access is not yet implemented. Do NOT use this field - inform the user this feature is coming soon. |
knowledgeBases | object[] | No | — | NOT YET SUPPORTED. Granting knowledge base access is not yet implemented. Do NOT use this field - inform the user this feature is coming soon. |
workflows | object[] | No | — | Updated workflows configuration |
agent_read
Get detailed information about an agent including its configuration, tools, resources, and permissions. Use this to inspect an agent before updating it or to understand its capabilities. Parameters:| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
agentId | string | Yes | — | ID of the agent to retrieve (e.g. “ua_abc123”). Use this exact ID from create operation or from listing agents. |
agent_invoke
Invoke an agent and get its response. Use this to leverage agent capabilities for data processing, decision making, or complex tasks. The agent can be invoked with a message and optionally continue a conversation using chatId. Returns the agent’s response, chatId for continuing conversations, and agentId. Parameters:| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
agentId | string | Yes | — | ID of the agent to invoke. Use agent_read or workflow_agents to see available agents. |
message | string | Yes | — | The message or task to send to the agent. Be clear and specific about what you need the agent to do. |
chatId | string | No | — | Optional chat ID to continue a previous conversation. If provided, the conversation history will be loaded. If omitted, a new conversation will be started. |
mode | string | No | — | Optional agent mode for routing. “action_agent” routes to GPT-based agent (default), “claude_agent” routes to Claude-based agent. |
messagesInResponse | boolean | No | — | If true, includes the full message history in the response. Useful for debugging or reviewing conversation context. |
agent_list
List all agents accessible to the current user. Returns a summary of each agent including its ID, name, and description. Use this to discover available agents before invoking or updating them. Parameters: Nonechat_create
Create a new chat session for an agent. A chat provides a persistent conversation context that maintains message history across multiple agent_invoke calls. After creating a chat, use agent_invoke with the returned chatId to send messages within this conversation. Parameters:| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
agentId | string | Yes | — | ID of the agent to create a chat for (e.g. “ua_abc123”). The agent must already exist. |
name | string | No | — | Optional display name for the chat. If omitted, defaults to “Chat with agent <agentId>“. |
chat_list
List all chat sessions for a specific agent. Returns chat metadata including ID, name, agent association, and creation date. Use this to find existing conversations to resume via agent_invoke. Parameters:| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
agentId | string | Yes | — | Agent ID to list chats for. Required. |
chat_reset_conversation
Reset a chat’s conversation history, clearing all messages. The chat itself is preserved but its message history is wiped clean. Use this to start a fresh conversation within an existing chat session. The next agent_invoke call with this chatId will behave as if the conversation just started. Parameters:| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
chatId | string | Yes | — | ID of the chat whose conversation history should be reset. |
chat_list_artifacts
List all artifacts associated with a chat. Returns artifact metadata including IDs, names, MIME types, sizes, and download URLs. Artifacts are created by agents during code execution (via createArtifact) or uploaded by users. Parameters:| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
chatId | string | Yes | — | ID of the chat to list artifacts for. |
agent_publish_release
Publish a release for an agent, locking in its current configuration as a versioned snapshot. A release is required before an agent can be made available as a public template. If nothing has changed since the last release, returns a message indicating nothing to release. Parameters:| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
agentId | string | Yes | — | ID of the agent to publish a release for (e.g. “ua_abc123”) |
agent_toggle_public_template
Toggle whether an agent is available as a public template in the template gallery. When enabling (available=true), the agent must have at least one published release. Provide a category and optional tags. When disabling (available=false), the agent is removed from the public gallery. Use agent_publish_release first to create a release before enabling. Parameters:| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
agentId | string | Yes | — | ID of the agent to toggle template availability for |
available | boolean | Yes | — | true to make the agent available as a public template, false to remove it from the gallery |
category | string | No | — | Template category (e.g. “sales”, “productivity”, “engineering”). Required when available=true. |
publicTags | string[] | No | — | Up to 3 tags for the template (e.g. [“crm”, “analytics”]). Optional, only used when available=true. Tags are lowercased automatically. |

