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 doesn't contradict. The description adds minimal behavioral context beyond annotations, stating it's a POST operation but not detailing effects like irreversible deletion or permissions required. With annotations covering safety, it adds some value but is sparse.

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 brief and front-loaded with the tool name and HTTP method, but it includes redundant formatting (brackets and parentheses) and lacks efficient structure. It could be more streamlined without sacrificing clarity.

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), no output schema, and low schema coverage, the description is incomplete. It fails to explain the outcome of removal, error conditions, or confirmation steps, leaving gaps for a mutation tool with significant behavioral implications.

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?

Schema description coverage is 0%, so the description must compensate. It lists 'sshKeyId' as a required parameter but provides no semantic details, such as what format the ID should be or where to obtain it. This leaves the parameter meaning unclear beyond the schema's basic type.

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 states the tool removes an SSH key ('sshKey.remove'), which is a specific verb+resource. However, it doesn't differentiate from sibling tools like 'dokploy_sshKey_delete' (which doesn't exist in the list) or other removal tools in the system, making it clear but not sibling-distinctive.

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?

No guidance is provided on when to use this tool versus alternatives. The description lacks context about prerequisites, such as needing an existing SSH key ID, or comparisons to other SSH key operations like 'dokploy_sshKey_create' or 'dokploy_sshKey_update'.

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