Skip to main content
Glama

delete_api_key

Destructive

Revoke a tenant API key so requests using that credential are no longer authorized.

Instructions

Revoke a tenant API key. Requests using that credential will no longer be authorized.

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": "delete_api_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
key_idYesUUID of the API key to revoke

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.4
    • changedInput schema / properties / key_id / description
      Previous value: -"UUID da API Key a revogar"New value: +"UUID of the API key to revoke"
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the danger profile is covered structurally. The description adds genuine value by scoping the blast radius (only requests bearing that credential lose authorization), but says nothing about irreversibility, whether a revoked key can be restored, or required permissions.

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 followed by the consequence. No filler, no repetition of the title or schema.

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?

A one-parameter destructive tool with full annotations and no output schema needs little more than this. The main missing piece is that revocation is permanent and unrecoverable — useful context for confirming before the call — but otherwise the definition is sufficient to invoke it correctly.

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 description coverage is 100% and the single key_id parameter is documented as 'UUID of the API key to revoke.' The description adds no meaning beyond the schema, so the baseline of 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?

States a specific verb and resource: 'Revoke a tenant API key.' The resource is unambiguous against the sibling set (delete_agent, delete_secret, delete_mcp_server, etc.), though it does not explicitly contrast with update_api_key as a non-destructive alternative.

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?

The description implies when to use it by describing the effect ('requests using that credential will no longer be authorized'), but it never states conditions, prerequisites, or when to prefer update_api_key over revocation. Usage must be inferred from consequence rather than stated.

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

Deploy Server

Other Tools