Skip to main content
Glama
MementoRC

MCP Git Server

by MementoRC

git_diff_staged

Review staged changes before committing in a Git repository using this tool. Identify modifications, additions, or deletions to ensure precise version control and accurate updates.

Instructions

Shows changes that are staged for commit

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repo_pathYes

Implementation Reference

  • Core handler function executing `repo.git.diff('--cached')` with options for stat_only, max_lines, name_only, and paths. Applies size limiting and formats output.
    def git_diff_staged(
        repo: Repo,
        stat_only: bool = False,
        max_lines: int | None = None,
        name_only: bool = False,
        paths: list[str] | None = None,
    ) -> str:
        """Get staged changes diff with file-specific and advanced options"""
        try:
            # Build git diff arguments
            diff_args = ["--cached"]
    
            # Add options based on parameters
            if name_only:
                diff_args.append("--name-only")
            elif stat_only:
                diff_args.append("--stat")
    
            # Add specific paths if provided
            if paths:
                diff_args.extend(["--"] + paths)
    
            # Execute git diff with arguments
            diff_output = repo.git.diff(*diff_args)
    
            # Handle name-only output
            if name_only:
                return (
                    f"Files with staged changes:\n{diff_output}"
                    if diff_output.strip()
                    else "No staged changes"
                )
    
            # Handle stat-only output
            if stat_only:
                return (
                    f"Staged changes summary:\n{diff_output}"
                    if diff_output.strip()
                    else "No staged changes"
                )
    
            # Apply size limiting for full diff output
            return _apply_diff_size_limiting(
                diff_output, "staged changes", stat_only, max_lines
            )
    
        except GitCommandError as e:
            return f"❌ Diff staged failed: {str(e)}"
        except Exception as e:
            return f"❌ Diff staged error: {str(e)}"
  • Pydantic input schema defining parameters: repo_path (required), stat_only, max_lines, name_only, paths.
    class GitDiffStaged(BaseModel):
        repo_path: str
        stat_only: bool | None = False
        max_lines: int | None = None
        name_only: bool | None = False
        paths: list[str] | None = None
  • Registers 'git_diff_staged' tool by creating a wrapped handler from git_diff_staged function with required repo and extra args.
    "git_diff_staged": self._create_git_handler(
        git_diff_staged,
        requires_repo=True,
        extra_args=["stat_only", "max_lines", "name_only", "paths"],
    ),
  • Initial tool registry entry for git_diff_staged with schema GitDiffStaged and metadata.
    ToolDefinition(
        name=GitTools.DIFF_STAGED,
        category=ToolCategory.GIT,
        description="Show changes that are staged for commit",
        schema=GitDiffStaged,
        handler=placeholder_handler,
        requires_repo=True,
    ),
  • Helper function used by git_diff_staged to limit large diff outputs, truncate by lines, and add warnings.
    def _apply_diff_size_limiting(
        diff_output: str,
        operation_name: str,
        stat_only: bool = False,
        max_lines: int | None = None,
    ) -> str:
        """Apply size limiting to diff outputs with consistent formatting"""
        if not diff_output.strip():
            return f"No changes detected in {operation_name}"
    
        if stat_only:
            # This should be handled by the caller using --stat flag
            return diff_output
    
        # Apply line limit if specified
        if max_lines and max_lines > 0:
            lines = diff_output.split("\n")
            if len(lines) > max_lines:
                truncated_output = "\n".join(lines[:max_lines])
                truncated_output += (
                    f"\n\n... [Truncated: showing {max_lines} of {len(lines)} lines]"
                )
                truncated_output += "\nUse stat_only=true for summary or increase max_lines for more content"
                return truncated_output
    
        # Check if output is extremely large and warn
        if len(diff_output) > 50000:  # 50KB threshold
            lines_count = len(diff_output.split("\n"))
            warning = f"⚠️  Large diff detected ({lines_count} lines, ~{len(diff_output) // 1000}KB)\n"
            warning += "Consider using stat_only=true for summary or max_lines parameter to limit output\n\n"
            return warning + diff_output
    
        return diff_output
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool 'shows changes', implying a read-only operation, but doesn't clarify if it's safe, what format the output is in, or any side effects. This is inadequate for a tool with potential complexity in Git operations.

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 that directly states the tool's purpose without any fluff. It's appropriately sized and front-loaded, 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 Git operations, no annotations, no output schema, and low parameter coverage, the description is incomplete. It doesn't address behavioral aspects like output format, error conditions, or how it interacts with sibling tools, leaving significant gaps for an AI agent.

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?

The description adds no parameter information beyond what the schema provides (a single 'repo_path' parameter). With 0% schema description coverage, the description doesn't compensate by explaining what 'repo_path' means or its format. However, since there's only one parameter, the baseline is slightly higher, but it still lacks meaningful semantic context.

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') and resource ('changes that are staged for commit'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'git_diff' or 'git_diff_unstaged', which would require mentioning it specifically shows staged changes versus unstaged or all changes.

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 like 'git_diff' or 'git_diff_unstaged'. It lacks context about prerequisites (e.g., needing a staged change) or exclusions, leaving the agent to infer usage from the name and description alone.

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

Related 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/MementoRC/mcp-git'

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