batuta-mcp
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| decompose_into_plansB | Split a brain dump into 2-5 plans with DISJOINT file boundaries (auto-corrects overlaps once). Returns plans, overlapsResolved, attempts. |
| check_boundary_overlapsC | Pure check: do any plans share file boundaries? Returns overlaps and ok. |
| scaffold_worktreesA | Validate (git repo, no overlaps, safe paths) then create a git worktree per plan and return a ready-to-paste prompt per plan. Set dryRun to preview without touching disk. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
TDQS
Scored across 3 tools
Each tool has a clear, distinct purpose: checking overlaps, decomposing input, and scaffolding worktrees. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern with snake_case, making them predictable and easy to understand.
Three tools is exactly right for the focused domain of plan decomposition and worktree setup. The scope is well-defined.
The tool set covers the full workflow: validation (check), creation (decompose), and execution (scaffold). There are no obvious gaps for its stated purpose.