local-kms-mcp-server

delete_key

Remove a key pair from the keystore using its unique key ID, with optional secure wipe to overwrite key files before deletion.

Instructions

Delete a key pair from the keystore

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": {
      "keyId": "<keyId>"
    },
    "name": "delete_key"
  }
}

Input Schema

Name	Required	Description	Default
`keyId`	Yes	Unique key identifier
`secureWipe`	No	Overwrite key file with random data before deletion

Output Schema

Name	Required	Description	Default
`keyId`	Yes	The deleted key ID
`success`	Yes	Whether deletion was successful

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0May 26, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations provided, and description fails to disclose that deletion is destructive and irreversible, or mention the secureWipe behavior which is critical for understanding side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single concise sentence, no fluff. Slightly lacks context but remains efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool is destructive and has an optional secureWipe parameter, the description lacks context about consequences, output, and when to use secureWipe. Output schema exists but is not referenced.

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%, so baseline is 3. Description adds no extra meaning beyond what the schema provides for keyId and secureWipe.

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 the action (delete) and resource (key pair), distinguishing it from sibling tools like check_keypair, generate_key, etc.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives (e.g., when to delete vs rotate), or any prerequisites or warnings.

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

Deploy Server