Dokploy MCP Server

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

Annotations indicate this is a non-readOnly, non-destructive, non-idempotent, openWorld operation, but the description adds no behavioral context beyond what annotations already provide. It doesn't explain what 'processing' entails, whether it's a transformation or validation, what side effects occur, or what the expected outcome is. For a mutation tool (readOnlyHint=false), this lack of behavioral description is a significant gap.

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 extremely brief (two lines) with no wasted words, but this brevity comes at the cost of being under-specified. While structured with the tool path and parameter list, it lacks the substantive content needed for understanding. It's concise but inadequately informative.

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 this is a mutation tool (readOnlyHint=false) with 2 undocumented parameters (0% schema coverage), no output schema, and no behavioral description, the description is completely inadequate. It fails to explain what the tool does, when to use it, what the parameters mean, or what to expect as a result. The annotations provide some safety profile, but the description adds almost no value.

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%, meaning neither parameter has any documentation in the schema. The description only lists parameter names ('base64', 'composeId') without explaining what they represent, what format 'base64' should contain, what a 'composeId' refers to, or how they interact. This provides essentially no semantic value beyond the bare parameter names already visible in the schema.

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 merely restates the tool name with minimal context ('[compose] compose.processTemplate (POST)'), providing no specific verb or resource explanation. It doesn't clarify what 'processTemplate' means or how it differs from sibling compose tools like 'dokploy_compose_deployTemplate' or 'dokploy_compose_getConvertedCompose'. This is essentially a tautology of the name with HTTP method added.

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 absolutely no guidance on when to use this tool versus alternatives. The description provides no context about prerequisites, typical use cases, or how it relates to other compose operations. With many sibling tools in the compose category, this leaves the agent guessing about appropriate selection.

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