Skip to main content
Glama
Sign In
conversation-branch

conversation-branch

by qddfxp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

cb_note

Idempotent

Update a branch's NOTES.md with new remarks to document experiment context.

Instructions

更新分支 NOTES.md 的备注

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": {
      "root": "<root>",
      "name": "<name>",
      "text": "<text>"
    },
    "name": "cb_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes实验分支名（只能用小写字母、数字、连字符；main 是保留名）
rootYesConversation Branch 工作区根目录
textYes要写入的备注内容

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

The description only says 'update' and does not explain whether NOTES.md is overwritten, appended to, created if missing, or whether the branch must already exist. Annotations already indicate readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so there is no contradiction, but the description adds very little behavioral context beyond those annotations.

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?

The description is a single short sentence with no filler, and the core action and target are front-loaded. It is concise, though it sacrifices helpful detail for brevity.

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?

For a simple note-update operation, the schema and annotations cover parameters and the side-effect profile reasonably well. However, the exact semantics of '更新'—whether it replaces the entire NOTES.md note or updates a specific portion—are not clarified, leaving some ambiguity for an agent.

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 documents all three parameters (root, name, text) with 100% coverage. The description adds no parameter-specific detail beyond what the schema provides, so the baseline 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 states a specific action ('更新') and a clear target ('分支 NOTES.md 的备注'), which is enough to distinguish this tool from sibling tools like cb_rename, cb_status, cb_log, and cb_diff. Despite being terse, it is unambiguous about what resource is affected.

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?

The description gives no guidance on when to use this tool versus alternatives, no preconditions, and no exclusions. It only states what the tool does, not the context in which it should be selected.

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

Deploy Server

Other Tools