Skip to main content
Glama
martinsky999

MCP Git Server

by martinsky999

git_diff

Compare changes between Git branches or commits to review modifications before merging or deploying code.

Instructions

Shows differences between branches or commits

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repo_pathYes
targetYes

Implementation Reference

  • Core handler function that computes the git diff against the specified target using repo.git.diff(target). Called by the MCP tool dispatcher.
    def git_diff(repo: git.Repo, target: str) -> str:
        return repo.git.diff(target)
  • Pydantic input schema for the git_diff tool, defining repo_path and target parameters.
    class GitDiff(BaseModel):
        repo_path: str
        target: str
  • Registration of the 'git_diff' tool (GitTools.DIFF) in the list_tools() method, including name, description, and input schema.
    Tool(
        name=GitTools.DIFF,
        description="Shows differences between branches or commits",
        inputSchema=GitDiff.schema(),
    ),
  • MCP call_tool dispatcher case for git_diff: extracts target, calls git_diff helper, formats and returns TextContent response.
    case GitTools.DIFF:
        diff = git_diff(repo, arguments["target"])
        return [TextContent(
            type="text",
            text=f"Diff with {arguments['target']}:\n{diff}"
        )]
  • Enum definition providing the tool name constant GitTools.DIFF = "git_diff" used in registration and dispatch.
    class GitTools(str, Enum):
        STATUS = "git_status"
        DIFF_UNSTAGED = "git_diff_unstaged"
        DIFF_STAGED = "git_diff_staged"
        DIFF = "git_diff"
        COMMIT = "git_commit"
        ADD = "git_add"
        RESET = "git_reset"
        LOG = "git_log"
        CREATE_BRANCH = "git_create_branch"
        CHECKOUT = "git_checkout"
        SHOW = "git_show"
        INIT = "git_init"
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool 'shows differences', implying a read-only operation, but doesn't disclose critical behaviors like output format, error handling, or whether it requires a clean working directory. This leaves significant gaps for a tool with no annotation support.

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, efficient sentence with zero wasted words. It's appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration, making it easy to parse quickly.

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 the complexity of a Git diff operation, no annotations, no output schema, and low schema coverage, the description is incomplete. It lacks details on return values, error conditions, and how it differs from sibling tools, making it inadequate for full contextual understanding.

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?

The input schema has 0% description coverage, and the description adds no meaning beyond the parameter names. It doesn't explain what 'repo_path' or 'target' represent (e.g., target could be a branch name, commit hash, or comparison like 'HEAD~1'), failing to compensate for the lack of schema documentation.

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 clearly states the verb 'shows differences' and the resource 'between branches or commits', making the purpose understandable. However, it doesn't explicitly distinguish this tool from its siblings like 'git_diff_staged' or 'git_diff_unstaged', which would require more specific differentiation to achieve a perfect score.

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. With siblings like 'git_diff_staged' and 'git_diff_unstaged' available, it fails to specify scenarios where this tool is preferred, such as for comparing arbitrary commits or branches, leaving usage context unclear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/martinsky999/mcp-git-py'

If you have feedback or need assistance with the MCP directory API, please join our Discord server