Bamboo MCP Server

Overview Schema Source Related Servers Discussions Admin

create_bamboo_specs_yaml

Generates a bamboo-specs YAML file to set up a CI/CD pipeline with build commands, Docker image, and deployment environments.

Instructions

Generate a bamboo-specs YAML pipeline configuration file.

Creates a complete bamboo-specs/bamboo.yaml that defines CI/CD pipeline. This file can be committed to the repository to configure the plan via Bamboo Specs.

Args: project_key: The Bamboo project key (e.g., 'PROJ') plan_name: Display name for the plan plan_key: Short key for the plan (e.g., 'BUILD') repository_url: Git repository URL branch: Default branch to build (default: 'master') build_commands: List of build commands to execute docker_image: Optional Docker image for build agent deployment_environments: Optional list of deployment environment names (e.g., ['DEV', 'SIT', 'UAT', 'PROD'])

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": {
      "project_key": "<project_key>",
      "plan_name": "<plan_name>",
      "plan_key": "<plan_key>",
      "repository_url": "<repository_url>"
    },
    "name": "create_bamboo_specs_yaml"
  }
}

Input Schema

Name	Required	Default
`branch`	No	master
`plan_key`	Yes
`plan_name`	Yes
`project_key`	Yes
`docker_image`	No
`build_commands`	No
`repository_url`	Yes
`deployment_environments`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 28, 2026

TDQS

A4/5.0

Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the tool 'generates' and 'creates' a file, but does not specify whether it overwrites existing files, any required permissions, or potential side effects (e.g., rate limits, destructive actions). This is insufficient for an agent to understand the tool's impact.

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 well-structured with a brief purpose statement followed by a detailed Args list. It is front-loaded and each sentence adds value. However, the Args section is somewhat verbose; while necessary for parameter clarity, it could be slightly shortened by grouping related info.

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

Completeness4/5

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

Given the tool has 8 parameters (4 required), no annotations, and an output schema (true), the description covers the generator's purpose, parameter details, and usage suggestion (commit to repo). It does not explain return values or error behavior, but the presence of an output schema partially mitigates that gap. Overall, it is fairly complete for a file generation tool.

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

Parameters5/5

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

The input schema has 0% description coverage, so the description fully compensates by listing each parameter in an Args section with clear explanations (e.g., 'project_key: The Bamboo project key (e.g., 'PROJ')'). This adds significant meaning beyond the schema's bare property names.

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 states 'Generate a bamboo-specs YAML pipeline configuration file' with specific verb and resource. It also mentions 'creates a complete bamboo-specs/bamboo.yaml that defines CI/CD pipeline', distinguishing it from sibling 'create_bamboo_specs_java' which likely produces Java-based specs.

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

Usage Guidelines4/5

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

The description implies usage context: 'This file can be committed to the repository to configure the plan via Bamboo Specs.' This indicates when to use the tool (to set up CI/CD pipeline via YAML Specs). However, it does not explicitly state when not to use it or provide alternatives beyond the sibling tool name.

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