Dokploy MCP Server

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

The description adds no behavioral information beyond what annotations provide. Annotations indicate this is a mutable (readOnlyHint: false), non-destructive (destructiveHint: false), idempotent (idempotentHint: true) operation with open-world semantics (openWorldHint: true). The description doesn't mention what gets updated, whether changes are immediate or require deployment, what permissions are needed, or any side effects. However, since annotations provide basic behavioral hints, the bar is lower, and the description doesn't contradict them.

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?

While technically concise (just two lines), the description is under-specified rather than efficiently informative. The first line '[mysql] mysql.update (POST)' wastes space on obvious information (the tool name and HTTP method), and the parameter list is a raw dump without organization or prioritization. The structure doesn't front-load important information about the tool's purpose or usage.

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 complex database update tool with 32 parameters, no output schema, and no annotations covering critical behavioral aspects (like whether updates require redeployment or affect running instances), the description is completely inadequate. It doesn't explain what happens after the update, what values are returned, whether the update is atomic, or how it interacts with other MySQL operations. The combination of high complexity and minimal description makes this tool difficult for an agent to use correctly.

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 32 parameters and 0% schema description coverage, the description provides only a bare parameter list without any semantic explanation. The schema documents types and constraints but not meaning. The description fails to explain what mysqlId refers to, what fields can be updated, how optional parameters interact, or the significance of swarm-related parameters. For a complex update operation with many parameters, this is severely inadequate.

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 only states '[mysql] mysql.update (POST)' followed by a parameter list, which essentially restates the tool name and HTTP method without explaining what the tool actually does. It doesn't specify what resource is being updated (a MySQL database instance/container) or what the update operation entails. This is tautological rather than providing meaningful purpose clarification.

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?

The description provides zero guidance on when to use this tool versus alternatives. With many sibling tools for different database types (mariadb, mongo, postgres, redis) and various MySQL operations (create, delete, deploy, start, stop), there's no indication of when this update tool is appropriate versus creating a new instance or using other MySQL tools. No prerequisites, dependencies, or contextual usage information is provided.

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