Skip to main content
Glama

bx_project_update

Idempotent

Apply one validated task edit to an exact revision while preserving old snapshots; no model call, so results stay stale until reanalysis.

Instructions

按精确版本编辑任务或设置,保留历史,不调用模型。 / Apply one validated task edit to an exact revision, preserving old snapshots. Does not call a model; results become stale until a new analysis.

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_id": "<project_id>",
      "revision": "<revision>",
      "request_id": "<request_id>",
      "command": "<command>"
    },
    "name": "bx_project_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
commandYes
revisionYes
project_idYes
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.3/5.0
Behavior4/5

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

Beyond the annotations (readOnly=false, idempotent=true, destructive=false), the description adds real behavioral context: history is preserved via old snapshots, no model is invoked, and downstream results go stale until re-analysis. It does not explain the request_id de-duplication contract that justifies the idempotent hint, which is the main remaining gap.

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?

Two short sentences, bilingual mirroring, with the core action front-loaded and the staleness caveat last. The Chinese and English halves are largely redundant for a single reader, but the total length is small and nothing is padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a high-complexity mutation tool with eight discriminated command shapes and revision-based concurrency, yet the description never enumerates what can be edited or how revision conflicts are handled. An output schema exists so return values need no explanation, but the input-side complexity is largely undocumented, leaving the agent to infer behavior from raw JSON Schema.

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% across four required parameters, so the description must carry the load — and it only gestures at 'exact revision' without explaining optimistic concurrency or stale-revision rejection. It says nothing about request_id or the eight command variants (edit/add/move/remove/mode/planning/relations/settings) whose only documentation is const/enum values in 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?

The description uses a specific verb and resource: 'Apply one validated task edit to an exact revision,' and the Chinese half adds that it also covers 'settings' (任务或设置). This is enough to distinguish it from read-oriented siblings like bx_project_get or analysis tools like bx_analysis_submit. It stops short of naming a competing write path such as bx_task_import, so it is clear but not sibling-differentiating.

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 phrase 'one validated task edit' implies edits must be pre-validated (presumably via bx_task_validate) and applied one at a time, and 'results become stale until a new analysis' tells the agent a follow-up analysis is needed. However, no explicit when-to-use/when-not or named alternative is given, so the guidance is implied rather than stated.

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