Atlassian Bamboo MCP Server

Overview Schema Source Related Servers Discussions Admin

bamboo_get_project

Retrieve specific Bamboo project details by providing its project key. Access project name, key, and configuration information.

Instructions

Get details of a specific Bamboo project by key

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": {
      "project_key": "<project_key>"
    },
    "name": "bamboo_get_project"
  }
}

Input Schema

Name	Required	Description	Default
`expand`	No	Fields to expand in the response
`project_key`	Yes	The project key (e.g., "PROJ")

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0May 29, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It accurately indicates a read operation ('Get details') but does not elaborate on permissions, rate limits, or side effects. It is accurate but lacks depth.

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 efficiently conveys the tool's purpose with a front-loaded verb. Every word is necessary, with no unnecessary elaboration.

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 lack of an output schema, the description could provide more context about what 'details' entails. The term is vague, and the agent may not know the exact response structure. Still, the tool is straightforward, so a score of 3 is reasonable.

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 already describes both parameters (project_key and expand) with full coverage. The description adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate.

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 'Get', the resource 'details of a specific Bamboo project', and the method 'by key'. It effectively distinguishes from sibling tools like bamboo_list_projects (which lists projects) and other get tools.

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 the tool should be used when you need full details of a single project identified by key. However, it does not explicitly state when not to use it or mention alternatives like bamboo_list_projects for listing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.