Skip to main content
Glama
MCP Dokploy Online
by igoruam

sshKey-all

Read-onlyIdempotent

Lists all SSH keys configured in a Dokploy instance, enabling you to review and manage access credentials through a single API call.

Instructions

GET /sshKey.all

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-all"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/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 structurally. The description adds nothing beyond that — no indication of whether secrets/public keys are included in the response, no pagination or volume expectations, and no auth requirements, which matters for an open-world read of key material.

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 single line is free of waste but is under-specified rather than concise; it is a raw endpoint dump with no natural-language framing. Size is appropriate only in the trivial sense that there is almost no content.

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?

For a simple zero-parameter read tool with no output schema, an agent still needs to know roughly what comes back (all SSH keys in the account? per-workspace?) and how it differs from the app-scoped sibling. The description supplies none of this, leaving the definition entirely dependent on annotations and the tool name.

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

Parameters4/5

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

The tool takes zero parameters and the schema is closed (additionalProperties: false), so there is no parameter meaning for the description to convey. Baseline 4 applies since nothing is missing on this dimension.

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 only the raw route string "GET /sshKey.all", which essentially restates the tool name (sshKey-all). At best an agent can infer 'list all SSH keys' from the path, but no verb+resource phrasing clarifies scope, and nothing distinguishes it from siblings like sshKey-allForApps or sshKey-one.

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 guidance, no mention of exclusions, and no pointer to alternatives such as sshKey-allForApps (which presumably filters by app) or sshKey-one (single key). The 'all' suffix hints at retrieving everything, but the agent must guess the conditions that select this tool over its siblings.

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