Loading ToolBench
MCP server for Atlassian Bamboo CI/CD platform
Server has 17 tools with consistent naming (verb_noun pattern) and descriptions present for all. However, input schemas lack depth: most parameters are minimally described, many lack type constraints (enums, ranges), and output schemas are not documented. Error handling exists but is generic. Parameter descriptions average ~40 chars, below the 72-char baseline for A+ tools. No tool annotations (readOnlyHint/destructiveHint). Composition is sound, tools are single-responsibility and chainable via IDs. Security: credentials injected via environment (good), but no per-tool permission declarations or audit logging visible.
Create a new Bamboo deployment project linked to a build plan
Get the build logs for a specific build. Returns log file URLs that can be accessed via browser.
Get the result of a specific build
Get build result with actual log content. For plan builds, fetches logs from all jobs. For job builds, returns logs directly.
Get details of a specific deployment project
Get a specific deployment result with optional logs
Output schemas not documented. LLMs cannot infer what fields to expect from tool responses, forcing them to guess at downstream field names and risking broken tool chains.
Parameter descriptions lack constraint details. 'plan_key' described as 'The plan key (e.g., "PROJ-PLAN")' but no format spec (length, character set, case sensitivity). LLMs cannot validate inputs without explicit constraints.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Agents cannot distinguish safe reads from destructive writes without explicit hints. bamboo_trigger_build and bamboo_trigger_deployment should be marked destructiveHint=true.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 58 | 2026-07-28+ | v2 |
Get deployment results for an environment
Get the latest build result for a plan
Get details of a specific plan branch
Check Bamboo server health status
List build results with optional filters
List all Bamboo deployment projects
List all branches for a Bamboo build plan
Get Bamboo server information including version, edition, and state
Stop a running build for a Bamboo plan
Trigger a build for a Bamboo plan
Trigger a deployment to an environment
Error handling is generic (formatError utility). No recovery guidance. When a build trigger fails, LLM receives no hint whether to retry, check permissions, or ask the user. Errors should categorize as retryable/user-fixable/fatal.
No per-tool permission declarations. Tools like bamboo_trigger_build and bamboo_stop_build should declare required scopes (e.g., 'write:builds'). Enables least-privilege agent config and audit trails.