Skip to main content
Glama
Sign In
worktree-tools-mcp

worktree-tools-mcp

by georgeasoto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

cleanup_worktree

Remove a git worktree and optionally delete its associated branch. Automatically cleans up any empty parent directories left behind.

Instructions

Remove a git worktree and optionally delete its branch. Automatically cleans up empty parent directories.

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": {
      "worktreePath": "<worktreePath>"
    },
    "name": "cleanup_worktree"
  }
}

Input Schema

NameRequiredDescriptionDefault
cwdNoOptional: Working directory (defaults to current directory)
deleteBranchNoOptional: Also delete the local branch (default: false)
worktreePathYesPath to the worktree to remove

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses the removal action, optional branch deletion, and automatic cleanup of parent directories. Could mention error behavior or idempotency.

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

Conciseness5/5

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

Two concise sentences, no wasted words. Front-loaded with the primary action, followed by a key behavioral detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers the main behavior and additional cleanup, but lacks details on error cases, return value, or preconditions. With no output schema, description could be slightly more complete.

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

Parameters4/5

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

100% schema coverage provides basic parameter meanings. Description adds value by explaining the optional deleteBranch behavior and the automatic cleanup, going beyond the schema.

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

Purpose5/5

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

Clearly states the verb (remove), resource (git worktree), and adds optional branch deletion and automatic cleanup of empty parent directories. Distinguishes from sibling tools like create_worktree and list_worktrees.

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 explicit guidance on when to use this tool versus alternatives or any prerequisites. The description only states what it does, not when it should be used.

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

Deploy Server

Other Tools