Skip to main content
Glama

Delete agent

delete_agent
Destructive

Remove a developmental agent from this mount.

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_idYesThe developmental agent's id, from create_agent.
request_idNoOptional. Your id for this call. Repeat it to retry safely: the same request_id is never charged twice.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / agent_id / description
      Added value: +"The developmental agent's id, from create_agent."
    • addedInput schema / properties / request_id / description
      Added value: +"Optional. Your id for this call. Repeat it to retry safely: the same request_id is never charged twice."
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is carried by structured data. The description adds only the mount-scoping detail and says nothing about permanence, what happens to the agent's associated state or records, or whether the caller needs any confirmation step — the things that matter most for an irreversible mutation.

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?

A single front-loaded sentence with no filler, which is the right shape for a simple destructive call. It is efficient but borders on under-specified rather than genuinely tight, so it does not reach 5.

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

Completeness2/5

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

For a destructive, non-idempotent mutation the description should disclose consequences and any preconditions; it discloses neither. An output schema exists so return values need no explanation, but irreversibility and the fate of related data are left entirely to inference.

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?

Schema description coverage is 100%, and the agent_id field already points back to create_agent while request_id documents retry safety, so the schema does the heavy lifting. The description contributes no additional meaning about either parameter; baseline 3 applies.

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

Purpose4/5

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

Specific verb plus resource ('Remove a developmental agent') with a scope qualifier ('from this mount'), which clearly separates it from create_agent, list_agents, and get_agent. It stops short of clarifying what distinguishes a 'developmental' agent from any other agent, which is the one ambiguity an agent might hit.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance and no mention of alternatives or prerequisites (e.g., whether the agent must be stopped first, or whether a non-destructive retire path exists among the siblings). The agent must infer all of this from the name alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.