Skip to main content
Glama
Sign In
Git MCP Server

Git MCP Server

by EnesOzturk11
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get Git Diff

get-git-diff

Retrieve line-by-line Git differences from a repository. Optionally include staged changes or focus on a single file.

Instructions

Get all difference in files and show the differences line by line. It can focus on a specific file according to willingness

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": {
      "repoPath": "<repoPath>"
    },
    "name": "get-git-diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
cachedNoShow difference that are taken to stage
repoPathYesGitHub repository path
targetFileNoShow difference only this file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It mentions line-by-line output and optional file focus, but fails to specify whether diffs are against HEAD, how the cached flag affects output, or any side effects. This lacks critical behavioral context for an agent.

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 two sentences and front-loads the primary purpose. However, phrases like 'according to willingness' and 'all difference' are awkward and could be clearer, though it is not overly verbose.

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 absence of an output schema and annotations, the description should provide more context about return format, default diff scope, and interaction with cached. It leaves significant gaps for an agent to invoke it correctly.

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 descriptions cover all parameters (100%), so the baseline is 3. The description adds little beyond restating targetFile's purpose; it does not clarify cached behavior or repoPath requirements.

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 clearly states the tool retrieves file differences and displays them line by line, with optional file-specific focus. This distinguishes it from siblings like get_git_status (status overview) and get_git_log (history).

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?

The description implies its use for viewing diffs but does not explicitly state when to prefer it over alternatives like get_git_status or get_git_log. No exclusion or alternative guidance is provided.

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