Skip to main content
Glama
Claude Free Code MCP

Claude Free Code MCP

by ImIpscanning

git_create_branch

Destructive

Create and switch to a new local Git branch after approval, so you can isolate changes without altering the current branch.

Instructions

Create and switch to a new local Git branch after local approval.

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": {
      "branch": "<branch>"
    },
    "name": "git_create_branch"
  }
}

Input Schema

NameRequiredDescriptionDefault
branchYesNew branch name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=false, so the mutation/safety profile is carried by structured data rather than the text. The description adds the 'switch to' side effect and the 'after local approval' gating hint, but says nothing about behavior when the branch already exists, uncommitted working-tree changes, or that this is purely local (no remote tracking/creation).

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 front-loaded sentence with the verb and object up front and no filler. 'After local approval' is slightly ambiguous as to who approves and how it affects invocation, but overall it is tight and readable.

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

Completeness3/5

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

For a one-parameter tool whose annotations already flag destructiveness, the description is close to sufficient. Missing though are the key failure/side-effect cases an agent needs — existing branch name, dirty working tree, and confirmation that no remote branch is created.

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% for the single parameter, so the schema already documents 'branch' as the new branch name. The description adds no naming conventions, format, or validation semantics beyond what the schema provides, making 3 the correct baseline.

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?

States a specific verb pair (create and switch) and a specific resource (new local Git branch), which is enough to distinguish it from git_branches (listing) and git_commit. It stops short of 5 only because 'local' vs remote and the relation to sibling tools is left implicit.

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 by 'new local branch' — an agent can infer this is for branching off the current HEAD rather than pushing to a remote. There is no explicit when-to-use/when-not guidance and no named alternative for inspecting existing branches (e.g. git_branches).

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