Skip to main content
Glama

bx_project_create

Idempotent

Create and save a full parent/child task as a new isolated B-335 project, preserving original text and returning its project ID and version.

Instructions

保存新项目,保留原文并返回项目ID与版本。 / Save a full parent/child task as a new isolated B-335 project. Idempotency key binds exact input. Does not call a model.

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": {
      "request_id": "<request_id>",
      "input": "<input>"
    },
    "name": "bx_project_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
request_idYes

Output Schema

NameRequiredDescriptionDefault
dataYes
kindYes
productYes
api_versionYes
business_decisionYes
execution_authorizationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0-rc.9-linux.1

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, and the description adds real context beyond them: the idempotency key binds the exact input, no model is invoked (so no inference cost/latency), and the original text is retained. It does not describe failure modes or what happens on a key collision with differing input.

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?

Short and front-loaded, with the core action first and behavioral caveats after. The bilingual duplication adds length without adding information for an English-reading agent, but nothing is padded.

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?

An output schema exists, so omitting return details is acceptable, and the description does note the ID/version return. However, for a tool with a large nested input at 0% schema coverage, the description leaves too much of the payload semantics unexplained.

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

Parameters2/5

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

Schema description coverage is 0% and the input is a deeply nested object (nodes, dependencies, dictionaries, retained, profile_id). The description only glosses 'request_id' as an idempotency key and hints that 'retained' preserves original text; the parent/child node structure, dependency kinds, and dictionary sha256 binding are left entirely to the schema.

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?

States a specific verb and resource ('Save a full parent/child task as a new isolated B-335 project') and adds the return contract (project ID and version). It implicitly separates itself from bx_project_update via 'new isolated', but never names a sibling explicitly.

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?

Usage is only implied by 'new isolated project' and the note that it 'does not call a model', which usefully rules out an analysis path. There is no explicit when-to-use/when-not guidance pointing at bx_project_update or bx_task_import for the alternative flows.

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