@lodd/mcp-server

revoke_api_key

Permanently deactivate an API key to stop it from working immediately. Use with a key ID from list_api_keys; this action cannot be undone.

Instructions

Permanently deactivate an API key. The key will immediately stop working. Use list_api_keys to find key IDs. Cannot be undone.

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

Input Schema

Name	Required	Description	Default
`key_id`	Yes	The UUID of the key to revoke (from list_api_keys)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.15Jul 28, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Discloses irreversibility and immediate effect ('permanently', 'cannot be undone', 'immediately stop working'). No annotations present, so description carries full burden and handles it well.

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 concise sentences with no waste, front-loaded with core action and immediate consequences.

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?

Given simple operation, description covers purpose, prerequisites, and consequences completely. No output schema needed. Sibling tools provide additional context.

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 has one parameter with description; tool description adds context by linking to list_api_keys, enhancing understanding beyond schema alone.

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?

Description clearly states 'Permanently deactivate an API key' with specific verb and resource, and distinguishes from siblings like list_api_keys and create_api_key.

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?

Explicitly instructs to use list_api_keys to find key IDs, providing clear context. No explicit exclusions or alternatives, but simple action makes it adequate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.