Bamboo MCP Server

by mvadly

Overview Schema Source Related Servers Discussions Admin

Python

Remote

create_project

Create a new Bamboo project by specifying a unique key and name. Optionally add a description for the project.

Instructions

Create a new Bamboo project.

Args: key: Project key (uppercase letters, e.g., 'MYPROJ') name: Project name description: Optional project description

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": {
      "key": "<key>",
      "name": "<name>"
    },
    "name": "create_project"
  }
}

Input Schema

Name	Required	Description	Default
`key`	Yes
`name`	Yes
`description`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 28, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations provided. Description does not disclose side effects, destruction potential, or authentication needs. Creation tools typically imply mutation, but no details about irrevocability or limits.

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?

Extremely concise: one-line purpose followed by parameter documentation. No wasted words. Front-loads the action.

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?

Adequate for a creation tool with output schema (not explained). Missing error cases, idempotency, or relationship to other resources like plans.

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?

Despite 0% schema coverage, the description lists all three parameters with format requirements (e.g., key as uppercase letters). Adds value beyond bare schema by clarifying the key format and that description is optional.

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 'Create a new Bamboo project' with a specific verb and resource. It distinguishes from siblings like list_projects which are read operations.

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. Does not mention that key must be unique or that project creation requires specific permissions.

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