Skip to main content
Glama

security-crypto

crypto_keypair_generate

Generate fresh Ed25519 or RSA-2048/4096 PKCS#8/SPKI PEM keypairs and SHA-256 public key fingerprints via Node crypto.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "crypto_keypair_generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
rsaBitsNo
algorithmNoed25519

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses the underlying implementation (Node crypto) and output encodings, but says nothing about whether the private key is returned, whether keys are persisted, entropy/security caveats, cost of RSA-4096 generation, or the overall response shape. For a key-material-producing tool this leaves important behavior unstated.

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?

A single dense sentence with no filler, and the core purpose plus output formats are front-loaded. Slightly overpacked with format acronyms, but nothing is wasted.

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?

It covers what is produced (keypair plus fingerprint) and in what encodings, which is the essential information for a two-parameter generator with no output schema. It still omits return structure and the private-key handling caveats that matter for a cryptographic generation tool with zero annotation coverage.

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 0%, so the description must compensate for two undocumented parameters. It does broaden rsaBits semantics by naming the supported sizes (2048/4096) and ties the algorithm enum to Ed25519/RSA, but it never states that rsaBits only applies when algorithm is 'rsa', nor that ed25519 ignores it.

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?

The description uses a specific verb and resource ('Generate fresh ... keypairs') and names the algorithms, encodings (PKCS#8/SPKI PEM), and the derived SHA-256 fingerprint. That is enough for an agent to distinguish it from sibling audit/inspect tools, though it never explicitly contrasts itself with any of them.

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?

There is no when-to-use or when-not-to-use guidance, no mention of alternatives, and no hint about when to prefer ed25519 over rsa or which rsaBits to pick. 'Fresh' weakly implies new-key creation rather than inspecting existing keys, but the agent must infer everything else.

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