Skip to main content
Glama
Sign In
Atlassian Bamboo MCP Server

Atlassian Bamboo MCP Server

by norus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

bamboo_disable_plan

Disable a Bamboo build plan using its plan key to stop triggering builds for that plan.

Instructions

Disable a Bamboo build 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_disable_plan"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description must disclose all behavioral traits. It only says 'disable' without explaining immediate effects (e.g., prevents new builds? stops running builds?), permissions required, or reversibility. This is minimal and relies on the name for understanding.

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, concise and front-loaded. It earns its place by stating the core purpose, but could be slightly more informative without becoming verbose.

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

Completeness2/5

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

Given the tool's simplicity (one param, no output schema), the description lacks completeness. It does not explain the outcome of disabling a plan, mention potential side effects, or clarify differences from similar tools. An agent would need additional context from the tool name alone.

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 covers 100% of parameters with a clear description for plan_key. The description adds no additional meaning beyond the schema, 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.

Purpose4/5

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

The description 'Disable a Bamboo build plan' clearly states the action and resource, differentiating it from siblings like bamboo_enable_plan. However, it adds no information beyond the tool name itself, which limits differentiation from other mutation tools like bamboo_stop_build.

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 distinguishing it from bamboo_stop_build or prerequisites like needing the plan to exist. It only states what it does, leaving an AI agent without context for appropriate usage.

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