Skip to main content
Glama

git_worktree_sandbox

Create, merge, or discard isolated Git worktrees for agent experiments, keeping the main workspace safe from accidental changes or corruption.

Instructions

Creates, merges, or discards isolated git worktrees so agent experiments never corrupt main workspace.

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": {
      "action": "<action>"
    },
    "name": "git_worktree_sandbox"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
task_nameNoName of the sandbox task

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the key behavioral guarantee that worktrees are isolated and the main workspace is protected. However, it says nothing about what 'discard' destroys (uncommitted changes, branches), whether 'merge' can conflict or fail, or what permissions are needed for a mutating git operation.

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?

A single front-loaded sentence with zero filler: the verbs come first and the rationale follows. It is efficient, though packing the rationale in means the missing 'list' action and parameter behavior go unmentioned.

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?

This is a multi-action tool with a required enum, one partly undocumented parameter, no annotations, and no output schema, yet the definition is one sentence. Critical details an agent needs — destructive effects of discard, merge failure modes, and the list action's return shape — are absent.

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 coverage is only 50%: 'task_name' is documented in the schema but the required 'action' enum has no per-value description, and the description covers only three of its four values. The description adds no meaning about how task_name scopes a sandbox or how each action pairs with it, so it fails to compensate for the coverage gap.

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?

The description states a specific resource (isolated git worktrees) and three concrete verbs (creates, merges, discards), so an agent can immediately tell what the tool manipulates. It omits the fourth enum action, 'list', and gives no sibling differentiation, but the sibling names are unrelated tools so that is not a practical gap.

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

Usage Guidelines4/5

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

The clause 'so agent experiments never corrupt main workspace' supplies a clear motivating context for when to reach for this tool: risky or experimental work that must be isolated. There are no explicit when-not conditions or named alternatives, which keeps it below a 5.

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