Skip to main content
Glama

generate_key

Create an SSH key in your Detour vault and return its public key for authorized_keys while the private key stays protected.

Instructions

Create a key in the person's vault (needs vault:edit). Returns its public key, e.g. for authorized_keys; the private key never leaves Detour.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
algorithmNoed25519 (default), rsa or ecdsa.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries full burden and does deliver real value: it discloses the required permission (vault:edit), that the response contains the public key, and that the private key never leaves the server. It stays silent on mutation semantics that matter for a create operation — what happens if a key with the same name already exists, whether creation is idempotent, and error behavior.

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 tight clauses with zero filler, and the action plus its permission requirement is front-loaded before the return-value note. Every phrase earns its place.

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?

For a simple two-parameter mutation tool with no annotations and no output schema, the description covers permissions, return value, and a confidentiality guarantee, which is a good baseline. The significant gap is the unexplained 'name' parameter and the absence of duplicate-name behavior, both of which affect correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: the 'algorithm' property is described in the schema, but 'name' has no description anywhere. The description never explains what 'name' designates (vault label, filename, key identifier) or whether it must be unique, so it fails to compensate for the coverage gap.

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: 'Create a key in the person's vault', plus the required scope 'vault:edit'. It is unambiguous and no sibling deals with keys, so collision risk is low, but it does not explicitly distinguish itself from any 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?

Usage is only implied via an example ('e.g. for authorized_keys'), which hints at the intended context of exporting a public key. There is no explicit when-to-use statement, no exclusions, and no named alternatives for related operations such as listing or removing keys.

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