Skip to main content
Glama

delete_agent

Destructive

Archive an agent to remove it from listings and stop it responding; restore it later through the Zihin console because this server has no restore option.

Instructions

Archive an agent: remove it from listings and stop it responding. Restore through the Zihin console; this server has no restore tool.

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": "delete_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYesUUID of the agent to archive

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.4
    • changedInput schema / properties / agent_id / description
      Previous value: -"UUID do agente a arquivar"New value: +"UUID of the agent to archive"
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds what those hints do not: the operation is an archive (soft removal from listings plus stopped responses) and the recovery path is out-of-band via the console. It leaves open whether related data such as memories or sessions survive, and does not note that repeat calls are not idempotent, so it stops short of a 5.

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?

Two short sentences with no filler. The core effect is front-loaded and the recovery constraint follows immediately where an agent would look for it.

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 single-parameter destructive tool with full annotation coverage and no output schema, the description covers effect, irreversibility within this server, and the recovery channel. The only meaningful gap is whether the agent's memory, sessions, or credentials are also affected by archiving.

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

Parameters3/5

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

There is only one parameter (agent_id) and schema description coverage is 100%, with the schema itself stating it is the UUID of the agent to archive. The description adds no format, sourcing, or lookup guidance beyond that, so the baseline of 3 applies.

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?

"Archive an agent" states a specific verb and resource, and the following clause spells out the observable effect (removed from listings, stops responding). This also disambiguates the tool from a hard delete, which matters given the name delete_agent and siblings like delete_agent_memory or update_agent.

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 makes the use case clear (permanently take an agent out of service) and adds a real constraint: restoration is only possible through the Zihin console because this server has no restore tool. It stops short of naming an alternative such as update_agent for a reversible disable, so it is clear context rather than a full when/when-not routing rule.

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

Deploy Server

Other Tools