Skip to main content
Glama
Sign In
Bamboo MCP Server

Bamboo MCP Server

by mvadly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_build_result

Retrieve the result of a specific build using its build key. Obtain status and details from Bamboo CI/CD without manual navigation.

Instructions

Get the result of a specific build.

Args: build_key: The build result key (e.g., 'PROJ-PLAN-123')

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": {
      "build_key": "<build_key>"
    },
    "name": "get_build_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
build_keyYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It does not disclose behavioral traits such as read-only nature, permission requirements, or error handling for invalid build_key.

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?

Description is short and front-loaded with purpose. Two sentences plus Args section, no unnecessary words. 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 output schema exists and only one parameter, description is adequate but lacks usage context or guidance on when to use this vs sibling tools. Could be more complete for a search tool.

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?

Provides parameter description for build_key with example value 'PROJ-PLAN-123', which adds meaning beyond input schema. Since schema coverage is 0%, this compensates well.

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?

Description clearly states verb 'Get' and resource 'result of a specific build'. It distinguishes from siblings like get_build_log and list_build_results by focusing on result retrieval, though no explicit differentiation.

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 vs alternatives like list_build_results or get_build_log. No context about prerequisites or when not to use.

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