Skip to main content
Glama

Hail Communication for AI

Delete an agent

delete_agent
DestructiveIdempotent

Permanently delete a saved agent after explicit user authorization.

    A mismatched ``confirm_name`` returns an error without deleting anything.
    Numbers assigned to the deleted agent stop answering calls with it;
    texts are delivered to webhooks only.
    Pausing an agent is a separate non-deleting status change.
    Returns ``deleted``, ``agent_id`` and ``name``, or an error.

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

Input Schema

NameRequiredDescriptionDefault
agent_idYesSaved agent ID, from ``list_agents`` or ``create_agent``.
llm_modelNoModel ID of the calling agent. Optional. Recorded for analytics only.
confirm_nameYesThe agent's saved ``name``, as a safety check.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "Model ID of the calling agent. Optional. Recorded for analytics only.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well past the destructiveHint annotation by disclosing the confirm_name safety-check failure mode (error, nothing deleted) and downstream consequences: numbers stop answering, texts route to webhooks only. Return keys are also named.

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 irreversible action and authorization requirement, then each remaining sentence covers one distinct fact. The backtick markup and line breaks are slightly noisy but nothing is redundant.

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

Completeness5/5

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

For a destructive three-parameter tool with an output schema, this covers authorization, guard behavior, side effects, and return values. Nothing an agent needs before committing an irreversible delete is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds behavior the schema cannot: a mismatched confirm_name aborts the deletion with an error. That makes the guard parameter's role operationally meaningful.

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?

States a specific verb and resource ('Permanently delete a saved agent') with the critical scope qualifier that the deletion is permanent. That permanence framing alone distinguishes it from status changes on the same resource.

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

Usage Guidelines5/5

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

Gives an explicit precondition ('after explicit user authorization') and an exclusion: pausing is a separate non-deleting status change. The agent knows both when to call this and what not to use it for.

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.

Resources