Skip to main content
Glama
Pombus MCP Server

Pombus MCP Server

Official

Delete API key

delete_api_key
DestructiveIdempotent

Revoke an API key immediately and permanently, using the pod ID and key ID to scope the deletion so the key stops working at once.

Instructions

Revoke an API key. This cannot be undone and the key stops working 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": {
      "pod_id": "<pod_id>",
      "key_id": "<key_id>"
    },
    "name": "delete_api_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
key_idYes
pod_idYesA pod id the key can reach. The server rejects any id outside this key's scope.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already flag destructiveHint=true and readOnlyHint=false, but the description adds real value beyond them: that the action is irreversible and that the key stops working immediately. It leaves the idempotentHint=true claim unexplained (behavior when the key is already revoked), which keeps it from a 5.

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?

Two short sentences, front-loaded with the action and immediately followed by the most decision-relevant consequence. Nothing is redundant or padded.

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 two-parameter destructive tool with no output schema and fully populated annotations, the description covers the essential risk profile (irreversible, immediate effect). The remaining gap is the meaning of key_id and the scope rule for pod_id, which the description ignores entirely.

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?

The description says nothing about either parameter. With only 50% schema coverage, pod_id carries a useful scope constraint in the schema but key_id is completely undocumented, and the description does nothing to compensate for that gap.

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?

States a specific verb and resource ("Revoke an API key"), which cleanly separates it from create_api_key and list_api_keys without needing to name them. It stops short of 5 only because it doesn't explicitly position itself against the other delete_* siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the destructive warning: an agent can infer this is the tool for permanently disabling a key. There is no explicit when-to-use, no prerequisites (e.g. ownership/permission requirements), and no statement about alternatives such as rotating versus revoking.

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