Skip to main content
Glama

Revoke agent

revoke_agent
Destructive

Revoke an identity: it disappears from discovery (terminal) but its record is retained for auditability.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "revoke_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
didNoThe agent's DID; give this or agent_id.
agent_idNoYour stable id for the agent.

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: +"Your stable id for the agent."
    • addedInput schema / properties / did / description
      Added value: +"The agent's DID; give this or agent_id."
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false. The description adds important behavioral context beyond those annotations: the identity disappears from discovery, the action is terminal, and the record is retained for auditability.

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 a single, front-loaded sentence with no wasted wording. The key effect and auditability caveat are both stated compactly.

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?

Given the rich annotations, complete schema descriptions, and an output schema, the description does not need to explain parameters or return values. It adequately covers the terminal effect and audit retention, though it could additionally state permission requirements or what happens to credentials.

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 schema already explains that either did or agent_id may be supplied. The description adds no parameter-level meaning beyond what the input schema already provides, so the baseline 3 is appropriate.

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?

The description states a specific verb and resource: "Revoke an identity." It also clarifies the concrete effect (disappears from discovery, record retained), which distinguishes the operation from registration or discovery siblings without naming them explicitly.

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?

The terminal nature implies this is for permanent removal, but there is no explicit when-to-use guidance, no exclusions, and no comparison to sibling operations such as resolve or list registrations. The agent must infer the usage context.

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.