Dokploy MCP Server

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

Annotations cover read-only, non-destructive, idempotent, and open-world hints, so the agent knows it's a safe, repeatable query. The description adds minimal context with 'POST', but this doesn't contradict annotations—it's a neutral addition. However, it lacks details like rate limits or authentication needs, offering little beyond annotations.

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 concise but under-specified—it's a single bracketed phrase that fails to convey meaningful information. While brief, it lacks structure and front-loaded clarity, making it inefficient rather than helpful.

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 (implied by 'getUpdateData'), annotations provide safety hints, but there's no output schema. The description is too vague to explain what data is retrieved or its format, leaving significant gaps in understanding the tool's function and output.

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 (none). The description doesn't add parameter details, but since there are no parameters, a baseline of 4 is appropriate—it doesn't need to compensate for gaps.

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.getUpdateData (POST)' is tautological—it restates the tool's name and category without explaining what it does. It mentions 'POST' but lacks a clear verb and resource, failing to distinguish its purpose from sibling tools like 'dokploy_settings_getDokployVersion' or 'dokploy_settings_getWebServerSettings'.

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 does not mention any context, prerequisites, or exclusions, leaving the agent with no usage instructions.

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