local-kms-mcp-server

generate_key

Generate and store a new cryptographic key pair for a key ID, selecting from Ed25519 or ECDSA algorithms to enable local signing without external KMS.

Instructions

Generate and store a new key pair for the given key ID

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

Input Schema

Name	Required	Description	Default
`algo`	No	Key algorithm (default: ed25519)	ed25519
`keyId`	Yes	Unique key identifier

Output Schema

Name	Required	Description	Default
`publicKey`	Yes	Generated public key (base64-encoded DER/SPKI)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0May 26, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations provided; description only states 'generate and store' without disclosing overwrite behavior, authorization needs, or error handling. Minimal transparency for a mutation tool.

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?

Single sentence of 12 words, no fluff. Front-loaded with key action.

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

Completeness3/5

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

Output schema exists but not shown; description omits what is returned or stored. For a tool with 7 siblings and complex operation, more context needed.

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% with parameter descriptions; description adds no extra semantic value beyond schema. Baseline is 3.

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 uses specific verb ('generate and store') and resource ('new key pair') with scope ('for given key ID'). Clearly distinguishes from sibling tools like check_keypair, delete_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 Guidelines3/5

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

Implies usage for creating new key pairs but lacks explicit guidance on when to use vs alternatives (e.g., rotate_key) or when not to use (e.g., if key ID exists).

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

Deploy Server