Skip to main content
Glama
MCP Dokploy Online
by igoruam

server-withSSHKey

Read-onlyIdempotent

Retrieves server details with associated SSH key so you can configure access and deployment connections for Dokploy infrastructure.

Instructions

GET /server.withSSHKey

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": "server-withSSHKey"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.1/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered structurally; the literal "GET" merely echoes readOnlyHint. Beyond that, the description says nothing about what data comes back, whether keys are masked/redacted, or whether any authorization scope is required to read SSH material. Zero additional behavioral context is contributed.

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 conciseness. The single line is a raw route string with no natural-language front-loading of purpose, so nothing useful is delivered in the space it occupies.

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?

With no parameters and no output schema, the description bears the entire burden of explaining what this endpoint returns. It provides none of that, so an agent cannot predict the response shape or whether sensitive SSH data is exposed, which matters for handling and disclosure.

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 no parameters, so there is no parameter semantics for the description to explain. Baseline 4 applies for a zero-argument endpoint.

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?

"GET /server.withSSHKey" restates a route path rather than describing the operation in plain language. The token "withSSHKey" hints at SSH-key-related data for a server, but an agent cannot tell whether this returns servers that have SSH keys associated, returns a single server's key, or returns a URL/endpoint for SSH access. The scope is not differentiated from siblings such as server-one or server-security.

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 prerequisites, and no mention of when another sibling tool would be more appropriate. The agent is left to infer everything from the path fragment.

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