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. The description adds no behavioral context beyond what annotations provide. For a 'move' operation, the description should clarify what happens during the move (downtime? data transfer? service interruption?), whether it's reversible, authentication requirements, or any rate limits. With annotations covering basic safety profile, the description fails to add meaningful behavioral context for a potentially complex migration operation.

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 concise but arguably under-specified rather than efficiently structured. It wastes space on redundant information ('[postgres]' repeats the tool name prefix, '(POST)' is HTTP method detail less relevant to AI agents). The parameter listing is presented but without useful context. While brief, it fails to front-load the most important information about what the tool actually does.

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 'move' operation (potentially complex with data migration implications), no output schema, 0% parameter documentation coverage, and annotations that only provide basic safety hints, the description is severely incomplete. It doesn't explain what 'move' means operationally, what the expected outcome is, error conditions, or how to verify success. For a database migration tool, this leaves critical gaps in understanding how to use it 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?

Schema description coverage is 0%, so the schema provides no parameter documentation. The description lists parameter names but adds no semantic meaning - it doesn't explain what 'postgresId' refers to (database instance ID? cluster ID?), what 'targetEnvironmentId' means, what valid values are, or how these IDs should be obtained. For a move operation with 2 required parameters at 0% schema coverage, this minimal listing is insufficient to help an agent understand what to provide.

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 '[postgres] postgres.move (POST)' which is essentially a tautology - it repeats the tool name and adds HTTP method information without explaining what 'move' means in this context. It doesn't specify what resource is being moved (a PostgreSQL database/instance) or what 'move' entails (migration, relocation, transfer between environments). The parameter list provides some clues but doesn't constitute a purpose statement.

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 absolutely no guidance on when to use this tool versus alternatives. There are several sibling tools with 'move' operations (dokploy_application_move, dokploy_compose_move, dokploy_mariadb_move, dokploy_mongo_move, dokploy_mysql_move, dokploy_redis_move), but no indication of when this PostgreSQL-specific move tool is appropriate versus those other move operations. No prerequisites, constraints, or alternatives are mentioned.

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