Dokploy MCP Server

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

Annotations provide comprehensive hints: readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description doesn't contradict these (it mentions 'GET' which aligns with read-only). However, it adds minimal behavioral context beyond annotations - only implying it's a GET operation. No additional details about authentication needs, rate limits, or what specific Bitbucket data is retrieved are provided, leaving gaps despite good annotation coverage.

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 under-specified rather than concise. It uses a bracketed format '[bitbucket] bitbucket.one (GET)' followed by a parameter list, which is somewhat structured. However, the first line is redundant with the name/title, and the parameter listing adds little value without context. While not verbose, it fails to efficiently convey necessary information.

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 1 parameter with 0% schema coverage, no output schema, and annotations covering safety but not functionality, the description is incomplete. It doesn't explain what the tool returns (Bitbucket provider details, repository list, etc.), how the bitbucketId is used, or what 'bitbucket.one' refers to. For a tool in a complex system with many siblings, this leaves too much ambiguity about its specific role and output.

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 description must compensate. It only lists 'bitbucketId (string, required)' without explaining what this ID represents (provider ID, repository ID, configuration ID), where to find it, or its format. The description adds no meaningful semantics beyond what's minimally evident from the parameter name. With 0% schema coverage and inadequate parameter explanation, this falls below the baseline.

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 '[bitbucket] bitbucket.one (GET)' is essentially a tautology that restates the tool name and HTTP method. It doesn't specify what action is performed (retrieve, fetch, get details) or what resource is being accessed (a Bitbucket provider, repository, configuration). While it mentions 'bitbucket.one' and 'GET', it lacks a clear verb+resource statement that distinguishes this from sibling tools like 'dokploy_bitbucket_bitbucketProviders' or 'dokploy_bitbucket_create'.

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. There are multiple Bitbucket-related tools in the sibling list (e.g., 'dokploy_bitbucket_bitbucketProviders', 'dokploy_bitbucket_create', 'dokploy_bitbucket_update'), but the description doesn't indicate whether this tool retrieves a specific Bitbucket provider, fetches Bitbucket repositories, or serves another purpose. No context, exclusions, or prerequisites are mentioned.

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