Atlassian Bamboo MCP Server

by norus

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

bamboo_get_plan

Retrieve details of a Bamboo build plan by specifying its plan key. Get configuration, stages, and status information.

Instructions

Get details of a specific Bamboo build plan by key

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": {
      "plan_key": "<plan_key>"
    },
    "name": "bamboo_get_plan"
  }
}

Input Schema

Name	Required	Description	Default
`expand`	No	Fields to expand in the response
`plan_key`	Yes	The plan key (e.g., "PROJ-PLAN")

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0May 29, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Get details' without indicating whether the operation is read-only, what happens if the plan key is invalid, or any rate limits or side effects. More context is needed.

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

Conciseness4/5

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

The description is a single sentence that is concise and front-loaded. It earns its place but could be slightly more structured to improve readability, though it is already efficient.

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

Completeness3/5

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

Given the lack of an output schema and annotations, the description provides minimal context about what 'details' are returned. It is adequate for a simple retrieval tool but could mention that it returns plan configuration or settings for better completeness.

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

Parameters3/5

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

The input schema has 100% coverage, describing both parameters. The description does not add any additional meaning or examples beyond the schema definitions, so the baseline of 3 is appropriate.

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

Purpose5/5

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

The description clearly identifies the tool's function: 'Get details of a specific Bamboo build plan by key'. It uses a specific verb ('Get') and resource ('details of a specific Bamboo build plan'), and distinguishes it from sibling tools like batch listing or branch-specific retrieval.

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?

The description provides no guidance on when to use this tool versus alternatives, such as `bamboo_list_plans` for retrieving multiple plans or `bamboo_get_plan_branch` for branch details. No prerequisites or exclusions are mentioned.

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