Repository Manager

List

rm_worktree_list

Read-onlyIdempotent

List all git worktrees across workspace repositories, showing each session's branch and path so you can track concurrent development lanes without disturbing in-flight work.

Instructions

List (rm_worktree). Manage git worktrees for concurrent multi-session development (CONCEPT:RM-WORKTREE).

Each session works a repo in its own worktree on its own branch under <WORKTREE_ROOT>/<repo>/<branch> (shared .git, no re-clone), leaving the canonical checkout on its default branch so a working-tree reset never disturbs in-flight session work.

Input Schema

Name	Required	Description	Default
`base`	No	Base branch to fork from / sync against.	main
`into`	No	Target branch for 'merge', or the reset target for 'reset_branch'.	main
`path`	No	Workspace root override.
`repo`	No	Repo basename (e.g. 'epistemic-graph') or absolute path. Omit for 'list'/'prune' across all repos.
`adopt`	No	For 'add': move the canonical checkout's uncommitted WIP onto the new branch via a private ref (never the shared refs/stash stack).
`force`	No	For 'remove': override git's own dirty-tree refusal once lane occupancy has already cleared (never bypasses occupancy itself, D-CDX-15).
`repos`	No	For 'bulk_add': comma-separated repo basenames (default: every workspace repo).
`branch`	No	Worktree branch name (each session uses a distinct branch).
`strategy`	No	For 'sync': 'rebase' or 'merge'.	rebase
`stale_days`	No	For 'audit': an unmerged worktree quiet for longer than this many days is classified 'stale' (review) rather than 'active'.
`prune_merged`	No	For 'audit': DESTRUCTIVE. After classifying, remove every 'merged' worktree (and delete its branch) plus prune 'dangling' admin pointers. Never touches 'active'/'stale' work or orphaned directories.
`delete_branch`	No	For 'remove': also delete the branch.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.5.1Oct 19, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already establish read-only, idempotent, and non-destructive behavior, so the bar is lower. The description adds shared .git and canonical-checkout context, but does not disclose list-specific behavior such as filters, scope, or what the listing is based on, although an output schema exists.

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 definition is compact and front-loads 'List', then gives one concept paragraph. The content is relevant worktree context, though not specific to the list operation, and there is no obvious bloat.

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?

With an output schema and rich annotations, return values and safety profile need not be repeated. However, for a 12-parameter worktree tool surrounded by many siblings, the lack of usage guidance and operation-specific scope leaves it only adequately complete.

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?

Schema description coverage is 100%; all 12 parameters are documented in the schema, including defaults and per-action notes. The description adds no parameter semantics beyond the schema, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first token 'List' gives a verb, and the parenthetical ties it to rm_worktree, but the description never states what is listed or how the result differs from siblings like rm_worktree_audit, rm_worktree_prune, or rm_worktree_remove. The following paragraph describes worktree architecture rather than this tool's specific operation.

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 when-to-use, prerequisites, or alternatives are given. With many sibling worktree tools such as add, audit, prune, remove, and sync, the agent gets no routing guidance.

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

Deploy Server