Dokploy MCP Server

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

Annotations cover safety (readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true), so the bar is lower. The description adds minimal context by specifying it's a GET operation, but doesn't disclose behavioral traits like rate limits, authentication needs, or what data is returned. No contradiction with annotations exists.

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 operation type, but includes redundant formatting like brackets and parentheses. It wastes space on a parameter list without elaboration, though it avoids unnecessary verbosity.

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 tool's complexity (swarm node retrieval), lack of output schema, and low schema coverage, the description is incomplete. It doesn't explain return values, error conditions, or how it fits into the swarm context, leaving significant gaps for the agent.

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 'serverId' as optional but doesn't explain its purpose (e.g., to filter nodes by server), format, or impact. With one parameter and no schema details, the description adds little meaning beyond the schema's structure.

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 it's a GET operation for swarm nodes, which clarifies the verb and resource. However, it's vague about what 'getNodes' entails—whether it lists, retrieves details, or filters nodes—and doesn't differentiate from sibling tools like 'dokploy_cluster_getNodes' or 'dokploy_swarm_getNodeInfo', leaving ambiguity in purpose.

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 on prerequisites, such as needing swarm mode enabled, and doesn't mention sibling tools for comparison, leaving the agent without usage direction.

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