Skip to main content
Glama

Revoke this key

revoke_key
DestructiveIdempotent

Revoke the key making this request. It stops working at once and cannot be restored; polls it started stop at their next run. Use it when a key has leaked and you do not need a replacement. (DELETE /api/v1/me/key)

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_key"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known; the description goes further by disclosing immediacy ('stops working at once'), irreversibility ('cannot be restored'), and a non-obvious downstream side effect (polls it started stop at their next run). That side effect is exactly the kind of consequence an agent could not derive from structured data and is the most valuable line in the definition.

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?

Three short sentences ordered by importance: what it does, what happens as a result, then when to choose it. The endpoint reference in parentheses is cheap, clearly delimited, and does not interrupt the prose.

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 zero-parameter destructive operation with no output schema, the definition covers everything an agent needs: the target, immediacy, irreversibility, collateral effects, and a usage condition. No return-value documentation is required because none is structured.

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 tool takes zero parameters, so there is no parameter meaning to add and the baseline applies. The description correctly spends no words on arguments and instead documents consequences, which is the right allocation for an argument-free tool.

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 ('Revoke the key making this request') and pins down the exact scope of the key (the caller's own key, not an arbitrary key id). The phrase 'you do not need a replacement' implicitly contrasts with rotate_key, so an agent can separate the two destructive key operations without opening either schema.

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 an explicit triggering condition: a leaked key with no need for a replacement. That condition effectively routes away from rotate_key, but the sibling is never named, leaving the agent to infer the alternative from the condition rather than from an explicit statement.

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.