Skip to main content
Glama
MCP Dokploy Online
by igoruam

bitbucket-testConnection

Idempotent

Verifies Bitbucket credentials and workspace settings for a configured connection, helping confirm integration access before deployment workflows.

Instructions

POST /bitbucket.testConnection

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-testConnection"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiTokenNo
appPasswordNo
bitbucketIdYes
workspaceNameNo
bitbucketEmailNo
bitbucketUsernameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

Annotations already declare openWorldHint=true and idempotentHint=true, so the agent knows this makes an outbound network call that is repeatable. The description adds nothing beyond that: it does not disclose which credential combination is required (apiToken vs. appPassword plus email/username), whether it mutates or persists anything, rate-limit behavior, or what a failure looks like.

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 to the point of being empty; brevity here comes from under-specification rather than economy. A single bare endpoint string is not front-loaded with any actionable information.

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 6 undocumented parameters, a required identifier, and no output schema describing what a successful test returns, the definition is completely inadequate. An agent would have to guess at auth mode selection and result interpretation.

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

Parameters1/5

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

Schema description coverage is 0% across 6 parameters, so the description must carry the parameter burden – and it supplies zero information. It never explains the required bitbucketId or the mutually exclusive-looking authentication fields (apiToken, appPassword, bitbucketEmail, bitbucketUsername, workspaceName).

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 is literally "POST /bitbucket.testConnection" – it restates the tool name and HTTP verb/path rather than stating in prose what the tool verifies. An agent can infer 'test a Bitbucket connection' only from the name, not from any explanatory sentence.

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 prerequisites, and no differentiation from the many sibling testConnection tools (github-testConnection, gitlab-testConnection, gitea-testConnection, etc.). Nothing indicates whether this validates credentials, network reachability, or both, or when it should be called instead of application-saveBitbucketProvider.

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