Skip to main content
Glama

Revoke API key

apikey_revoke
Destructive

Revokes an API key immediately.

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": {
      "keyId": "<keyId>"
    },
    "name": "apikey_revoke"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyIdYesAPI key ID from apikey_list, not the key value.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / keyId / description
      Added value: +"API key ID from apikey_list, not the key value."
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this is a destructive write. The description adds a modest amount of context with 'immediately', implying the effect is instant with no grace period or undo, but it says nothing about whether revocation is reversible or what happens to in-flight requests using the key.

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 short sentence with the resource and effect front-loaded and no wasted wording. It is efficient, though the terseness leaves behavioral gaps rather than being over-long.

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

Completeness3/5

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

For a one-parameter destructive tool with annotations covering the safety profile, the definition is minimally sufficient. It omits consequences an agent would want before calling it, such as immediate loss of access for any service using the key and the absence of an undo path.

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 coverage is 100% and the schema already clarifies the parameter is the key ID from apikey_list, not the key value. The description adds nothing about the parameter, so the 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?

The description gives a specific verb and resource ('Revokes an API key') that an agent can match to intent without opening the schema. It stops short of distinguishing itself from siblings such as apikey_delete-adjacent or org/regtoken revoke tools, so it is clear but not differentiating.

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?

There is no guidance on when to revoke versus when to use apikey_create/apikey_list, nor any prerequisite or warning about confirming intent first. The only hint is the word 'immediately', which is not framed as usage advice.

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.