Skip to main content
Glama
MCP Dokploy Online
by igoruam

sshKey-update

Idempotent

Modify an SSH key's name or description in Dokploy by supplying its key ID, so stored keys stay identifiable and documented.

Instructions

POST /sshKey.update

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

Input Schema

NameRequiredDescriptionDefault
nameNo
sshKeyIdYes
lastUsedAtNo
descriptionNo

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 idempotentHint=true and openWorldHint=true, and the description adds nothing on top of them — no statement of which fields are mutable, what happens to omitted fields, whether lastUsedAt is client-settable, or what permissions are required. For a mutation tool with no destructiveHint, that silence is a real gap.

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 fragment is short but that is under-specification rather than conciseness; it conveys no information beyond the route already encoded in the tool name.

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?

A four-parameter mutation tool with no output schema, no annotation for destructive behavior, and zero schema descriptions requires the description to carry substantial weight. It carries none.

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 four parameters, and the description supplies no parameter meaning at all. The agent cannot tell from either source what 'lastUsedAt' or 'description' are for in an update context.

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.update" only restates the tool name as an HTTP route. It implies a mutation of an SSH key resource but names no updatable fields, no scope, and gives no way to distinguish it from siblings like sshKey-create or sshKey-generate beyond the word "update".

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. An agent must infer from the name alone that this modifies an existing key rather than creating or removing one.

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