Skip to main content
Glama
Sign In
Atlassian Bamboo MCP Server

Atlassian Bamboo MCP Server

by norus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

bamboo_stop_build

Stop a running build in Bamboo by providing the plan key. Prevents wasted resources on stuck or unnecessary builds.

Instructions

Stop a running build for a Bamboo plan

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

Input Schema

NameRequiredDescriptionDefault
plan_keyYesThe plan key to stop (e.g., "PROJ-PLAN")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

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 for behavioral disclosure. It mentions stopping a running build but omits details like whether the build is actually terminated or just flagged, what happens to in-progress steps, or any side effects.

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 concise sentence with no unnecessary words, but it could be structured to include more details without being verbose.

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?

For a simple one-parameter tool without an output schema, the description provides the basic purpose. However, it lacks behavioral context (e.g., idempotency, confirmation) that would help an agent use it correctly.

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?

Schema coverage is 100% for the single parameter 'plan_key', and its description is clear. The tool description does not add additional meaning beyond what the schema already provides, so a baseline score 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 uses a specific verb ('Stop') and resource ('running build for a Bamboo plan'), clearly distinguishing it from sibling tools like bamboo_trigger_build or bamboo_disable_plan.

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?

No guidance on when to use this tool versus alternatives (e.g., canceling a queued build vs. stopping a running one) or any prerequisites for stopping a build.

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