Dokploy MCP Server

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

Annotations already indicate this is a destructive (destructiveHint: true), non-idempotent (idempotentHint: false), open-world (openWorldHint: true) write operation (readOnlyHint: false). The description adds no behavioral details beyond these annotations, such as what specifically gets cleaned in Redis, potential side effects, or rate limits. However, since annotations cover key behavioral traits, the description doesn't need to repeat them, and there is no contradiction—it's neutral rather than misleading. A score of 4 reflects that annotations handle the transparency burden adequately, though the description could add context like 'clears all Redis cache data' to enhance value.

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—just a single line—but it's under-specified rather than efficiently informative. It wastes space on redundant elements like '[settings]' and '(POST)' without providing meaningful content. While brief, it lacks front-loaded clarity, making it less helpful despite its shortness. A score of 3 reflects that it's not verbose but fails to use its limited space effectively.

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 destructive nature (per annotations) and lack of output schema, the description is incomplete. It doesn't explain what 'cleanRedis' entails, what data is affected, or what the expected outcome is (e.g., success confirmation, error messages). For a destructive operation with no output schema, more context is needed to guide safe usage. The description falls short of providing necessary completeness for an agent to use it confidently.

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 zero parameters, and schema description coverage is 100% (empty schema). The description does not mention parameters, which is appropriate since none exist. According to the rules, with 0 parameters, the baseline score is 4, as there's no need for parameter semantics. The description neither adds nor detracts from parameter understanding.

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.cleanRedis (POST)' is tautological—it essentially restates the tool name and adds the HTTP method, which is redundant with annotations. It fails to specify what 'cleanRedis' actually does (e.g., clear Redis cache, reset settings, purge data) or distinguish it from sibling tools like 'dokploy_settings_cleanAll' or 'dokploy_settings_reloadRedis'. This leaves the purpose vague and unhelpful for an agent.

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 no guidance on when to use this tool versus alternatives. The description provides no context, prerequisites, or exclusions, and it doesn't reference any sibling tools (e.g., 'dokploy_settings_cleanAll' for broader cleanup). This absence of usage instructions makes it difficult for an agent to decide when this tool is appropriate.

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