Dokploy MCP Server

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

Annotations provide destructiveHint=true (indicating permanent deletion) and readOnlyHint=false (confirms mutation). The description adds the HTTP method (POST) which isn't in annotations, but doesn't elaborate on behavioral aspects like confirmation requirements, error conditions, or what 'aiId' represents. No contradiction with annotations, but minimal additional context.

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 but poorly structured. It includes the HTTP method and parameter list, but the formatting with brackets and line breaks is awkward. While concise, it lacks clear front-loading of the core purpose and reads more like a technical specification snippet.

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?

For a destructive operation with no output schema and 0% schema coverage, the description is inadequate. It doesn't explain the consequences of deletion, success/error responses, or relationship to other AI tools. Annotations cover safety aspects, but the description fails to provide necessary operational context.

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 schema provides no parameter documentation. The description only lists 'aiId (string, required)' without explaining what an AI ID is, where to find it, format constraints, or examples. This adds minimal semantic value beyond the bare 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 states 'ai.delete (POST)' which restates the tool name and HTTP method without explaining what resource it deletes. It mentions 'aiId' parameter but doesn't clarify this deletes an AI instance/model. Compared to siblings like 'dokploy_ai_create' and 'dokploy_ai_update', the purpose is only slightly distinguished by the 'delete' verb.

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 on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., existing AI to delete), when deletion is appropriate, or what happens after deletion. No comparison to sibling tools like 'dokploy_ai_remove' (not present) or other deletion tools in the system.

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