Skip to main content
Glama
Sign In
laravel13-livewire4.2.1-mcp

laravel13-livewire4.2.1-mcp

by shamimlaravel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

git_branch_create

Create a new git branch from an optional starting point, enabling isolated development and simpler version control.

Instructions

Create a new git branch.

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

Input Schema

NameRequiredDescriptionDefault
fromNo
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure, but it only states the base action. It does not mention side effects (e.g., does it checkout the new branch?), the meaning of 'from', or any potential failure modes. This is a minimal disclosure for a mutating operation.

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 a single sentence, front-loaded with the action, and contains zero extraneous words. It is as concise as possible while conveying the primary purpose.

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?

The tool is simple but the description is underspecified. No output schema exists, and there are no annotations. The description does not explain return values, success/failure behavior, or the optional 'from' parameter. For a mutation tool, this is incomplete.

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. It does not explain 'name' or 'from' beyond what the schema shows. The 'from' parameter is especially unclear—does it specify a base branch or a different repository? The description adds no parameter semantics.

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 'Create a new git branch' uses a specific verb and resource, clearly distinguishing it from sibling tools like git_branch_list, git_branch_merge, and git_branch_delete. It unambiguously states the action and target.

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 guidance is provided on when to use this tool versus alternatives. The description does not mention context, prerequisites, or exclusions. While the purpose is obvious, the description lacks any explicit or implicit usage direction beyond the literal action.

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