Skip to main content
Glama
MCP Dokploy Online
by igoruam

sshKey-remove

Destructive

Deletes an SSH key from Dokploy by ID, enabling access revocation and cleanup of unused credentials.

Instructions

POST /sshKey.remove

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

Input Schema

NameRequiredDescriptionDefault
sshKeyIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is covered by structured data. The description adds no behavioral context beyond the HTTP method: it does not say whether removal is permanent, whether it affects apps/deployments using the key, or whether confirmation is required — significant gaps for a destructive mutation.

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 certainly short, but it is a raw route string rather than a front-loaded explanation of purpose. Brevity here reflects under-specification, not efficient communication.

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 destructive, open-world mutation with a required identifier and no output schema, the definition supplies essentially nothing an agent needs: no effect description, no parameter meaning, no failure modes. The annotations carry all the usable signal.

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 required sshKeyId parameter, so the schema provides only the name and type. The description does not explain what identifier is expected (ID vs fingerprint vs name) or where to obtain it, leaving the parameter effectively undocumented.

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 "POST /sshKey.remove", which restates the tool name rather than explaining the operation. It does imply deletion of an SSH key, but gives no scope, effect, or differentiation from siblings like sshKey-update or settings-cleanSSHPrivateKey.

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 at all — no conditions, prerequisites, or named alternatives among the many sibling removal tools. An agent must infer everything from the tool name alone.

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