Dokploy MCP Server

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

Annotations provide strong behavioral hints: readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true, indicating a safe, repeatable read operation. The description adds minimal value by specifying 'GET', which aligns with read-only behavior but is redundant given annotations. It does not disclose additional traits like rate limits, authentication needs, or output format, though annotations cover core safety aspects adequately.

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 overly concise to the point of under-specification. While it uses only one short phrase, it fails to convey meaningful information beyond what's in the name/title. It lacks structure and does not front-load critical details, making it inefficient rather than appropriately concise.

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 (a read operation with no parameters) and rich annotations, the description is incomplete. It does not explain what 'Traefik config' entails, the scope (e.g., global vs. application), or the return format, and there is no output schema. Annotations cover safety, but the description fails to provide necessary context for effective use, especially compared to siblings.

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?

The tool has 0 parameters, with 100% schema description coverage (empty schema). The description does not discuss parameters, which is appropriate since none exist. It implies no input is needed, aligning with the schema. A baseline of 4 is justified as the description does not need to compensate for any parameter 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.readTraefikConfig (GET)' is tautological, essentially restating the tool name and title with minimal added context. It indicates a GET operation related to Traefik config in settings, but lacks a clear, specific verb-resource statement that distinguishes it from siblings like 'dokploy_settings_updateTraefikConfig' or 'dokploy_application_readTraefikConfig'. The purpose is vague beyond basic HTTP method and resource area.

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 no guidance on when to use this tool versus alternatives. It does not mention any prerequisites, context, or exclusions, nor does it reference sibling tools like 'dokploy_settings_updateTraefikConfig' (for updates) or 'dokploy_application_readTraefikConfig' (for application-specific config). Without such guidance, an AI agent cannot determine appropriate usage scenarios.

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