Fine Structure

Set Agent Status

set_agent_status

Destructive

Pause, resume or archive an agent. paused: it stops working and keeps its setup. archived: it is retired from the account; use this when the owner asks to delete an agent. active: it works again. Tasks that came due while it was paused or archived were paused themselves and stay paused: the result lists them, and update_agent_task with status active resumes each one.

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>",
      "status": "<status>"
    },
    "name": "set_agent_status"
  }
}

Input Schema

Name	Required	Description	Default
`status`	Yes
`agent_id`	Yes	The agent id, from list_agents.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, so the safety profile is known. The description adds the non-obvious payload: paused preserves setup, archived retires the agent from the account, and tasks that came due in the meantime are themselves paused and listed in the result — a real cascading side effect. It stops short of stating whether archive is reversible or whether the agent's data is retained.

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

Conciseness4/5

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

Front-loaded with the action, then status semantics, then the cascading-task caveat — a logical order with no filler. The colon-chained phrasing is dense but readable; a little tightening would make it a 5.

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?

For a two-parameter lifecycle tool with no output schema, it covers what each state does and even describes the response ("the result lists them"). The one material omission for a destructiveHint tool is whether archiving can be undone or how to restore an archived agent.

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

Parameters4/5

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

The schema only exposes the raw enum values active/paused/archived; the description defines each one's operational meaning (stops working but keeps setup / retired from account / works again), which is genuine added value. agent_id is already documented in the schema, so nothing is lost there.

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?

Opens with a specific verb triplet and resource: "Pause, resume or archive an agent." That instantly separates it from update_agent (field edits) and archive_agent_task (task-level) among the many agent-related siblings.

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?

Gives concrete routing guidance for the riskiest case — "use this when the owner asks to delete an agent" for archived — and names update_agent_task with status active as the follow-up for cascaded task pauses. It does not explicitly say when to prefer this over update_agent, which keeps it short of a 5.

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

All Fine Structure tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?