Dokploy MCP Server

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

Annotations indicate destructiveHint=true and readOnlyHint=false, so the agent knows this is a non-read-only, potentially destructive operation. The description adds no behavioral context beyond this, such as what 'destructive' entails (e.g., data loss, system impact) or any rate limits. It doesn't contradict annotations, but provides minimal additional value.

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, followed by a parameter list. It avoids unnecessary words, but the parameter details are minimal and could be more informative without sacrificing conciseness.

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 destructive annotations, 0% schema coverage, no output schema, and a mutation tool, the description is incomplete. It lacks details on what the tool returns, error conditions, or the effect of enabling/disabling cleanup, making it insufficient for safe and effective use.

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 parameters with types but no semantics—e.g., what 'enableDockerCleanup' does or when 'serverId' is needed. This adds little meaning beyond the schema, failing to address the coverage gap adequately.

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 updates Docker cleanup settings, which is a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'dokploy_settings_cleanDockerPrune' or 'dokploy_settings_cleanUnusedImages' that also relate to Docker cleanup, leaving the exact scope unclear.

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 server selection, and doesn't mention any sibling tools for comparison, leaving usage decisions ambiguous.

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