Repository Manager

Bulk Add

rm_worktree_bulk_add

Add git worktrees in bulk across workspace repos for concurrent sessions, isolating each task on its own branch without re-cloning.

Instructions

Bulk add (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.4/5.0

Behavior3/5

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

With annotations provided, the description adds useful context: worktrees share the same .git directory (no re-clone) and leave the canonical checkout untouched so resets do not disturb session work. However, it does not disclose behavior specific to the bulk_add operation, such as whether it creates one worktree per repo or how it interacts with existing worktrees.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is reasonably sized but front-loads a tautological label and then spends its second paragraph on generic worktree concept rather than the specific bulk_add operation. The concept is relevant background but could be more tightly focused.

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?

Despite an output schema and full parameter documentation, the description is incomplete for tool selection: it does not explain what bulk_add actually does, when to choose it over sibling worktree tools, or how the 'repos' parameter (default: every workspace repo) shapes the operation.

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%, so the schema already documents all 12 parameters. The description adds no parameter syntax or format details beyond the general worktree model, matching the baseline for high coverage.

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

Purpose2/5

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

The opening 'Bulk add (rm_worktree)' is largely a restatement of the tool name, and the rest explains the general worktree concept rather than what this specific tool does. It does not distinguish this tool from siblings like rm_worktree_add, rm_worktree_audit, or rm_worktree_prune, leaving the actual 'bulk add' behavior undefined.

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?

There is no guidance on when to use this tool versus alternatives such as rm_worktree_add or rm_worktree_audit. The context about concurrent multi-session development is background, not a selection rule or prerequisite.

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

Deploy Server