Skip to main content
Glama
Sign In
GitPilot MCP

GitPilot MCP

by Divyanshu-hash
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

apply_patch

Apply a git patch to incorporate code changes into the repository.

Instructions

Apply a git patch to the repository.

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": {
      "repo_path": "<repo_path>",
      "patch": "<patch>"
    },
    "name": "apply_patch"
  }
}

Input Schema

NameRequiredDescriptionDefault
repo_pathYes
patchYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose any behavioral traits, such as whether the patch is applied in-place, if it creates commits, or what happens on conflict. For a mutation tool, this is a significant gap.

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?

The description is a single sentence, concise, and front-loaded with the key action. However, its brevity sacrifices necessary detail, earning a slightly lower score.

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?

Given that applying a patch can have side effects like conflicts or failed merges, the description lacks completeness. No mention of failure modes, rollback, or related tools like 'check_for_conflicts' is provided, which would be essential for an agent.

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

Parameters1/5

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

The input schema has 0% description coverage, and the description does not elaborate on the parameters. It does not clarify the expected format of 'patch' (e.g., unified diff) or the path semantics of 'repo_path', leaving the agent with no additional meaning.

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 'Apply a git patch to the repository' uses a specific verb and resource, clearly indicating the action and target. It distinguishes well from sibling tools like 'check_for_conflicts' or 'commit_and_push', which serve different purposes.

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?

The description provides no guidance on when to use this tool versus alternatives, such as checking for conflicts first or committing after. An agent receives no context about prerequisites or typical workflows.

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