Skip to main content
Glama
MCP Dokploy Online
by igoruam

sshKey-generate

Idempotent

Generates RSA or Ed25519 SSH key pairs for authenticating to servers and enabling deployment access in Dokploy.

Instructions

POST /sshKey.generate

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": "sshKey-generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

Annotations supply idempotentHint=true and openWorldHint=true, but the description adds nothing: it does not say whether a private key is returned once, whether the key is persisted server-side, or whether the caller must store the material. For a credential-generating operation this is a serious omission, though the annotations at least signal repeat-call safety.

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

Conciseness2/5

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

It is short, but brevity here is under-specification rather than concision — a bare route string with no front-loaded statement of effect. Every useful fact is missing, so nothing "earns its place."

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

Completeness1/5

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

No output schema exists, so the description is the only place a caller could learn what comes back (public key, private key, fingerprint), and it says nothing. For a credential-generation endpoint, an agent cannot safely invoke or handle the result based on this definition.

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

Parameters1/5

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

Schema description coverage is 0% for the single parameter, so the description must compensate and does not. The rsa/ed25519 enum appears in the schema, but the description never mentions a default, valid values, or trade-offs between the two algorithms.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"POST /sshKey.generate" only restates the tool name as an HTTP route. It never says in plain language that an SSH key pair is generated, what algorithm choices mean, or how it differs from the sibling sshKey-create — an agent must infer the purpose entirely from the name.

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

Usage Guidelines1/5

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

No when-to-use, when-not-to-use, or alternative is named. With siblings like sshKey-create, sshKey-update, and sshKey-one present, the agent gets zero help deciding whether key generation is the right call or whether a key already exists.

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

Deploy Server

Other Tools