Skip to main content
Glama

revoke_account_api_key

Destructive

Immediately revoke one of your API keys. Requires OAuth security:write.

Consumers using the key will lose access. For rotation, first install and
test the replacement returned by rotate_account_api_key.

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": {
      "key_id": "<key_id>"
    },
    "name": "revoke_account_api_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
key_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations' destructiveHint=true, the description discloses the immediacy ('Immediately'), the blast radius ('Consumers using the key will lose access'), and a hard auth requirement ('Requires OAuth security:write') that annotations do not carry. This is exactly the operational context a mutating tool needs.

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, zero filler, with the action and its immediacy front-loaded, followed by impact and the rotation pointer. Every sentence earns its place.

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?

For a destructive, no-output-schema mutation the description covers action, auth requirement, user impact, and the related rotation workflow. The only real gap is how to source key_id, which is left entirely unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for key_id, so the description carries the full burden, and it adds nothing about the parameter — not its source, format, or how to obtain a valid id (e.g., via list_account_api_keys). 'One of your API keys' hints at identity but gives no usable semantics.

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?

The description leads with a specific verb+resource pair ('Immediately revoke one of your API keys') and the scoping word 'one of' makes clear this targets a single key rather than a bulk operation. It is clearly distinguishable from sibling tools like rotate_account_api_key and list_account_api_keys.

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?

It names the alternative (rotate_account_api_key) and the condition that selects it ('For rotation, first install and test the replacement'), which effectively routes the agent. It does not state an explicit when-not-to-revoke case, so it falls just short of full when/when-not coverage.

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.