Skip to main content
Glama

weavegraph_plan_worktrees

Partition files and tasks across parallel coding-agent git worktrees using min-cut graph optimization to prevent agents from editing coupled files.

Instructions

Partition files and tasks across K parallel coding agent git worktrees using min-cut graph optimization.

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": {
      "repo_path": "<repo_path>"
    },
    "name": "weavegraph_plan_worktrees"
  }
}

Input Schema

NameRequiredDescriptionDefault
tasksNo
repo_pathYes
num_agentsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations and no output schema, so the description carries the full burden and mostly fails it: nothing says whether this writes anything to disk, whether it creates the worktrees or only plans the split, what permissions or prior indexing are required, or what the response contains. The only behavioral signal is the implied computational nature of 'partition... using min-cut graph optimization'.

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?

One sentence, front-loaded with the action and resource, with no padding. It is arguably too terse for a three-parameter planner with zero schema documentation, but nothing in it is wasted.

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?

With no annotations, no output schema, and zero parameter documentation, the description leaves the agent without the input shape of nested task objects or any sense of the returned assignment. For a tool whose whole value is its output mapping of tasks to worktrees, that is a substantial gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate and only partly does: 'K parallel coding agent git worktrees' hints that num_agents is that K, and 'files and tasks' hints at the tasks array. It says nothing about repo_path needing to exist/be indexed, nor about the nested task_id/title/target_files fields that drive the partition.

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

Purpose4/5

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

Specific verb (partition) plus resources (files and tasks) and target (K parallel git worktrees), with the method (min-cut graph optimization) named. An agent can tell this is a work-scheduling/partitioning tool rather than an indexing or verification one, though it never states what the partition result is returned as.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: call it before spawning K agents and give it tasks plus a repo path. There is no explicit when-to-use-vs-alternatives statement, no mention of prerequisites such as an indexed repo (a sibling is weavegraph_index_repo), and no exclusion conditions.

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