Skip to main content
Glama
MCP Dokploy Online
by igoruam

sshKey-create

Creates and registers an SSH key pair for an organization in Dokploy, storing the required name, public key, private key, and optional description for deployment access.

Instructions

POST /sshKey.create

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>",
      "privateKey": "<privateKey>",
      "publicKey": "<publicKey>",
      "organizationId": "<organizationId>"
    },
    "name": "sshKey-create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
publicKeyYes
privateKeyYes
descriptionNo
organizationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/5

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

Annotations supply only openWorldHint=true and a title, so the description carries the full behavioral burden and delivers none of it. It does not say what is created, whether the supplied privateKey is stored server-side, what permissions or organization scoping are required, or what happens on duplicate names.

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 only because it is under-specified: a bare REST path with no verb, resource, or context sentence. Nothing is front-loaded because there is no substantive content.

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?

For a five-parameter mutation tool with four required fields, zero schema documentation, no output schema, and no destructive/read-only annotations, the description leaves essentially everything to guesswork.

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% across five parameters, four of them required, and the description adds no meaning. The crucial semantics — that privateKey and publicKey must be supplied by the caller rather than generated, and how organizationId scopes the key — are nowhere documented.

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 endpoint string "POST /sshKey.create", which restates the tool name (sshKey-create) rather than explaining it. An agent can infer that a write creating an SSH key is involved, but nothing distinguishes it from sshKey-generate or settings-saveSSHPrivateKey, which plausibly also persist key material.

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 prerequisites, and no mention of alternatives or exclusions. The agent must guess whether this creates a keypair, registers an externally supplied key, or stores credentials for an organization.

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