Dokploy MCP Server

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

Annotations indicate destructiveHint=true and readOnlyHint=false, which the description does not contradict. However, the description adds no behavioral context beyond what annotations provide, such as what 'clean' entails (e.g., deletion, removal, or resetting of SSH private keys) or any side effects like data loss or system impact.

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

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

The description is overly concise to the point of being cryptic, consisting of a single bracketed phrase. It lacks proper sentence structure and fails to front-load essential information, making it inefficient for quick understanding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the destructive nature (destructiveHint=true) and lack of output schema, the description is incomplete. It does not explain the outcome, such as what 'clean' means or what happens post-execution, leaving gaps in understanding for a potentially high-impact operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0 parameters and 100% schema description coverage, the schema fully documents the input structure. The description does not add parameter semantics, but since there are no parameters to explain, a baseline score of 4 is appropriate as no additional information is needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description '[settings] settings.cleanSSHPrivateKey (POST)' is tautological, essentially restating the tool name and title with minimal additional context. It mentions 'settings' and 'POST' but lacks a clear verb and specific resource explanation, failing to distinguish from sibling tools like 'dokploy_settings_saveSSHPrivateKey' or other cleanup tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus alternatives. It does not mention prerequisites, timing, or sibling tools like 'dokploy_settings_cleanAll' or 'dokploy_sshKey_remove', leaving the agent without context for selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.