Skip to main content
Glama

delete_secret_key

delete_secret_key
DestructiveIdempotent

Permanently delete an inactive secret key that is not selected for webhooks, from the connected test app. Deactivate it first; select a replacement if it is the current webhook 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": {
      "id": "<id>"
    },
    "name": "delete_secret_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe full 12-character ID returned by list_secret_keys.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, so the description doesn't need to argue irreversibility. It still adds real context beyond them: deletion is permanent, the key must already be inactive, webhook-selected keys are excluded, and the operation targets only the connected test app.

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 sentences, zero filler, with the destructive scope and preconditions front-loaded ahead of the conditional replacement clause.

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 single-parameter destructive tool with annotations and no output schema, the description supplies the preconditions an agent needs to avoid a failed or unsafe call. It could still say what happens if the key is active or webhook-selected, but the essentials are covered.

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 single 'id' parameter is fully documented there, including its 12-character format and provenance from list_secret_keys. The description adds no meaning 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?

States a specific verb and resource ('Permanently delete ... secret key') plus tight qualifiers (inactive, not webhook-selected, connected test app), so the operation is unmistakable. It doesn't explicitly contrast itself with siblings like update_secret_key or list_secret_keys, which keeps it short of a 5.

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?

'Deactivate it first; select a replacement if it is the current webhook key' gives concrete preconditions and an ordering the agent must follow before calling. It stops short of naming the tool that performs the deactivation/replacement, but the implied workflow is clear.

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.

Resources