Skip to main content
Glama
Sign In
Bamboo MCP Server

Bamboo MCP Server

by mvadly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_plans

Retrieve build plans from Bamboo, with optional filtering by project key to focus on specific projects.

Instructions

List build plans, optionally filtered by project key.

Args: project_key: Optional project key to filter plans (e.g., 'PROJ')

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_plans"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_keyNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, and the description only covers the basic listing behavior. It does not disclose details such as pagination, ordering, permissions, or rate limits, which are not addressed by the output schema.

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 concise with two short sentences, front-loading the main purpose and filtering option. Every word is necessary and no redundancy.

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 presence of an output schema and a single optional parameter, the description covers the core functionality. However, it lacks details on default behavior (lists all plans when no filter), ordering, or pagination, which could improve completeness.

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

Parameters4/5

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

The single parameter 'project_key' is described as an optional filter with an example value 'PROJ', adding meaning beyond the schema which only defines its type and default. This clarifies usage.

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 the verb 'list' and resource 'build plans', and mentions optional filtering by project key. It effectively distinguishes from sibling tools like 'list_projects' and 'get_plan'.

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

Usage Guidelines3/5

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

The description implies usage for listing plans with optional filtering but provides no explicit guidance on when to use this tool versus alternatives like 'get_plan' for a single plan or 'list_projects' for projects.

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