Spaceship MCP

update_agent

Modify an agent's name, description, system prompt, or tool list. Provide new values for any field to update the agent's configuration.

Instructions

Update an agent's name, prompt, or tools.

Providing description re-runs server-side prompt scaffolding and overwrites the current system prompt. Providing prompt sets it directly. Providing tools replaces the full tool list.

Args: agent_id: The agent's UUID. name: New display name. description: New description — triggers re-scaffolding. prompt: New raw system prompt. tools: Replacement list of tool UUIDs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "agent_id": "<agent_id>"
    },
    "name": "update_agent"
  }
}

Input Schema

Name	Required	Description	Default
`agent_id`	Yes
`name`	No
`description`	No
`prompt`	No
`tools`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.5May 5, 2026

TDQS

A4.5/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description discloses key behaviors: description re-runs scaffolding, prompt sets directly, tools are fully replaced. It lacks details on permissions, atomicity, or immediate effect, but is sufficient for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise: a one-line summary followed by clear bullet-like parameter explanations. Every sentence adds value, and the structure is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers all parameters and their behavioral traits. However, it lacks information about the return value (no output schema) and does not mention error conditions or side effects on ongoing runs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds significant meaning beyond the raw schema by explaining the effect of each parameter (e.g., 'triggers re-scaffolding', 'replacement list'). This compensates for the 0% schema description coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it updates an agent's name, prompt, or tools, with specific verb and resource. It distinguishes from sibling tools like create_agent (creation) and delete_agent (deletion).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains when to use each parameter (e.g., description triggers re-scaffolding, prompt sets directly, tools replaces list). However, it does not explicitly state when not to use this tool or contrast with alternatives beyond the parameter behaviors.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server