Skip to main content
Glama
MCP Dokploy Online
by igoruam

bitbucket-one

Read-onlyIdempotent

Fetches one Bitbucket integration by its ID from Dokploy so you can inspect its configuration for deployment or infrastructure management.

Instructions

GET /bitbucket.one

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "bitbucketId": "<bitbucketId>"
    },
    "name": "bitbucket-one"
  }
}

Input Schema

NameRequiredDescriptionDefault
bitbucketIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered structurally; the description adds nothing on top (no auth requirements, no error behavior, no rate-limit or side-effect notes). It is consistent with the annotations but contributes no behavioral context of its own.

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?

It is short, but that brevity reflects under-specification rather than efficiency; there is no front-loaded statement of purpose and no structure beyond a raw route string. Nothing is wasted because almost nothing is said.

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

Completeness1/5

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

For a tool with one undocumented required parameter and no output schema, the description should explain what is retrieved and what the identifier denotes; instead it offers only an HTTP verb and path. An agent cannot call this reliably without trial and error.

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

Parameters2/5

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

Schema description coverage is 0% for the single required parameter, so the description must carry the burden and does not: it never explains what bitbucketId refers to, its format, or where to obtain it. Only the self-descriptive parameter name gives an agent any foothold.

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 method and path ("GET /bitbucket.one") without saying what resource is fetched or what the result represents; it effectively echoes the tool name/title. An agent can infer a read of a Bitbucket-related object keyed by id, but nothing distinguishes this from siblings like bitbucket-getBitbucketBranches or bitbucket-bitbucketProviders.

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

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no mention of prerequisites or alternatives, and no indication of when this tool should be preferred over the many sibling bitbucket tools. The agent is left to guess entirely from the name.

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