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

worktree-tools-mcp

by georgeasoto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_worktree

Automatically create a git worktree for a given ticket and branch, with dependency installation and .env file copying. Organizes worktrees in a separate directory.

Instructions

Create a new git worktree with automatic setup. Auto-detects username from GitHub/git, installs dependencies, and copies .env files. Worktrees are created at ../-worktrees/username/TICKET/branch-name

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": {
      "ticket": "<ticket>",
      "branchName": "<branchName>"
    },
    "name": "create_worktree"
  }
}

Input Schema

NameRequiredDescriptionDefault
cwdNoOptional: Working directory (defaults to current directory)
ticketYesTicket number (e.g., CO-4493, PROJ-123)
openIdeNoOptional: Open worktree in IDE after creation
branchNameYesBranch name (spaces will be converted to hyphens, e.g., "billing feature" -> "billing-feature")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description must disclose behavioral traits. It mentions auto-detection, dependency installation, and .env copying, but does not cover prerequisites (e.g., existing git repo), error handling, or potential side effects.

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?

The description is three sentences, front-loads the main action, and contains no redundant information. Every sentence adds value.

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?

Given 4 parameters, no output schema, and no nested objects, the description covers the tool's purpose, behavior, and output path. It lacks details on error conditions or prerequisites, but is otherwise complete for a creation tool.

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 coverage is 100%, so the baseline is 3. The description adds context about automated setup beyond parameter descriptions, but does not significantly enhance parameter-level understanding beyond what the schema already provides.

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?

The description clearly states the tool creates a git worktree with automatic setup, including auto-detection of username, dependency installation, and .env copying. It distinguishes from siblings like list_worktrees or cleanup_worktree by focusing on creation.

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?

The description implies usage for creating worktrees but does not explicitly state when to use this tool versus alternatives like create_pr or list_worktrees. No when-not-to-use or exclusion criteria are provided.

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