Skip to main content
Glama
Sign In
Atlassian Bamboo MCP Server

Atlassian Bamboo MCP Server

by norus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

bamboo_enable_plan

Enable a Bamboo build plan by providing its plan key to allow builds to run again.

Instructions

Enable 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_enable_plan"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations present, the description bears full responsibility for transparency. It fails to disclose whether enabling is idempotent, what happens if the plan is already enabled, or any side effects on build queue or triggers.

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

Conciseness5/5

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

The description is a single sentence that directly states the tool's action without any verbosity. It is appropriately front-loaded and 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 tool's simplicity (one parameter, no output schema), the description covers the core purpose. However, it lacks behavioral context such as idempotency or state change implications, which would improve completeness for an agent.

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 description coverage is 100% for the single parameter 'plan_key', which already has a clear description in the schema. The tool description adds no additional meaning beyond what the schema provides, earning a baseline score of 3.

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 that the tool enables a Bamboo build plan, using a specific verb and resource. It effectively distinguishes from the sibling tool 'bamboo_disable_plan', making the purpose unambiguous.

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 like 'bamboo_disable_plan' or other plan lifecycle tools. No prerequisites or conditions for enabling are mentioned.

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