Skip to main content
Glama
MCP Dokploy Online
by igoruam

sshKey-one

Read-onlyIdempotent

Retrieves a specific SSH key by its ID from a Dokploy instance so you can inspect key details for deployment or infrastructure management.

Instructions

GET /sshKey.one

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": {
      "sshKeyId": "<sshKeyId>"
    },
    "name": "sshKey-one"
  }
}

Input Schema

NameRequiredDescriptionDefault
sshKeyIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered by structured data. The description contributes nothing beyond that — no note on what happens with an unknown ID, whether the key material is returned, or any auth/rate-limit context. With annotations carrying the burden, this barely clears the floor.

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?

The text is short but only because it is empty of content, not because it is efficient. Four words stating a route are not front-loaded explanation of behavior; this is under-specification rather than conciseness.

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?

There is no output schema, so the description should at least indicate what a successful call returns (a single key object? the private key?). For a read tool with an unidentified parameter and no return-value context, the definition leaves the agent without enough to call or interpret it reliably.

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 description coverage is 0% for the single parameter sshKeyId, and the description does not compensate at all. It never says whether sshKeyId is a numeric ID, a UUID, or a fingerprint, nor how to obtain it (e.g., from sshKey-all). The 1-parameter baseline of 4 is not warranted because the needed clarification is absent.

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?

The description is just the HTTP route "GET /sshKey.one", which restates the tool name rather than explaining what it does. An agent can infer it retrieves a single SSH key (contrasted with the sibling sshKey-all), but that inference comes from the name and siblings, not from the description itself. No verb-object statement of purpose beyond the raw endpoint.

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?

There is no when-to-use guidance, no mention of alternatives such as sshKey-all, and no prerequisites or exclusions. The agent must guess the selection condition entirely from the tool name.

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