Skip to main content
Glama
MCP Dokploy Online
by igoruam

bitbucket-bitbucketProviders

Read-onlyIdempotent

Retrieves configured Bitbucket providers from Dokploy so you can identify available repository integrations for deployment workflows.

Instructions

GET /bitbucket.bitbucketProviders

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bitbucket-bitbucketProviders"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=true, so the safety profile is covered structurally. The description adds nothing beyond the HTTP verb: it does not say what a 'provider' record contains, whether this hits a live Bitbucket endpoint, or whether results are cached or paginated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single line is not bloated, but it is under-specified rather than concise. There is no front-loaded statement of effect or return content, so brevity here is a deficit rather than a virtue.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter read with no output schema, the description should at least say what the call returns and what a Bitbucket provider represents. Instead it leaves an agent guessing about the response shape, which is the main thing needed to use the result correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters and schema coverage is 100%, so there is no parameter semantics for the description to compensate for. Per the zero-parameter baseline, this dimension is adequately handled by the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description only restates the endpoint as 'GET /bitbucket.bitbucketProviders', echoing the tool name rather than stating in plain language what the tool returns. An agent can infer it retrieves Bitbucket provider data, but there is no verb-plus-resource phrasing or scope detail to distinguish it from siblings like gitea-giteaProviders or application-saveBitbucketProvider.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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 such as bitbucket-testConnection or the other provider-listing siblings. The read-only HTTP verb weakly implies a listing/fetch operation, but no conditions, prerequisites, or exclusions are stated.

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

Deploy Server

Other Tools