Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-cleanSSHPrivateKey

Idempotent

Clears the stored SSH private key from Dokploy settings, removing sensitive credentials when access is no longer needed.

Instructions

POST /settings.cleanSSHPrivateKey

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": "settings-cleanSSHPrivateKey"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.2/5.0
Behavior2/5

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

Annotations declare openWorldHint=true and idempotentHint=true but say nothing about destructiveness, and the description adds no context about what is removed, whether the cleared private key affects SSH connectivity, or whether the action is reversible. For an operation named "clean" that presumably mutates credential state, this is a meaningful disclosure gap the description needed to fill.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is minimal to the point of being empty; it is trivially short but not front-loaded with any useful information. Conciseness here is a byproduct of under-specification rather than tight writing.

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 output schema, no parameters, and a description consisting solely of an endpoint path, an agent gets essentially no information about the effect or result of calling it. A settings-level key-cleaning operation needs at least a sentence on consequence and return behavior.

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, so the schema carries no semantic burden and the baseline is 4. Nothing about parameters could reasonably be added.

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 "POST /settings.cleanSSHPrivateKey", which restates the tool name rather than explaining it. It never says what "clean" means here—whether it deletes the stored private key, scrubs it from config, or just resets cached state—so the verb is not interpretable by an agent.

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives such as settings-saveSSHPrivateKey or settings-cleanAll despite those siblings existing. An agent has no basis to choose this tool over the other settings-clean* tools.

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