conversation-branch
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cb_statusA | 查看工作区状态（会就地重建 STATE.md 视图与 updated 时间戳，不改分支数据、版本号与 HEAD） |
| cb_checkA | 体检工作区结构（只读）：报告孤儿分支目录、缺失 PROMPT.md、归档缺失等问题 |
| cb_logA | 查看工作区事件时间线（只读） |
| cb_diffA | 生成分支 PROMPT 与父版本（或主线）的规则差异（写入分支 DIFF.md，不改主线） |
| cb_compareA | 生成多分支横向对比（写入 COMPARE.md，不改主线） |
| cb_initA | 初始化工作区（在 root 下建立 .branches/ 与主线） |
| cb_branchA | 创建实验分支，默认复制同源 inputs |
| cb_checkoutA | 切换 HEAD 到指定分支（实验期间主线只读，HEAD 决定谁可以被改动） |
| cb_noteB | 更新分支 NOTES.md 的备注 |
| cb_renameC | 重命名实验分支 |
| cb_discardA | 舍弃实验分支：names 指定要舍弃的分支，keep 指定保留的赢家（其余全舍弃）；names 与 keep 互斥，必须给其一。默认归档到 archive/，加 purge 则真删目录（不可恢复）。舍弃 HEAD 所在分支时 HEAD 自动回 main |
| cb_promoteA | 把实验分支提升为新主线：旧主线归档、版本号 +1（必须由用户明确批准）。note 为必填的提升理由，写入主线 CHANGELOG.md 供事后审计 |
| cb_rollbackA | 把主线回滚到某个归档版本：ref 可以是版本号或 archive/ 下的目录名（必须由用户明确批准） |
| cb_exportA | 导出分支交接包（不改工作区状态）：生成自带上下文的目录，可交给全新对话测试 |
| cb_verdictA | 把外部测试结论回流到分支 VERDICT.md（只记录，不执行 promote/discard） |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Most tools have clearly distinct purposes: status/check/log all inspect but target different aspects (state, health, timeline). diff/compare are separable as single-branch vs multi-branch analysis. Only minor boundary overlap exists between status and check, but descriptions clarify the distinction.
All tools use the unified cb_ prefix followed by a short imperative verb (rename, status, check, log, diff, compare, init, branch, checkout, note, discard, promote, rollback, export, verdict). The pattern is completely consistent and predictable.
15 tools is at the upper boundary of the ideal range, but each tool maps to a distinct operation in the branch lifecycle: init, create, inspect, modify, archive, promote, rollback, export, and verdict review. No tool feels redundant or unnecessary for the stated domain.
The surface covers the full branch workflow: creation, checkout, status, health checks, timeline, diffs, comparisons, naming, notes, discard, promotion, rollback, export, and external verdict ingestion. The only notable gap is the lack of a dedicated tool to update or edit the branch PROMPT itself, though that may be intentionally left to direct file editing.