Skip to main content
Glama
Claude Free Code MCP

Claude Free Code MCP

by ImIpscanning

git_diff

Read-only

Read unstaged or staged Git diffs, optionally for a specific file, to inspect pending changes with output capped at 96 KB.

Instructions

Read unstaged or staged Git diffs; outputs are limited to 96 KB.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "git_diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNoOptional file path
stagedNoShow staged changes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this as a safe read-only, closed-world operation, so the description's main added value is the 96 KB output cap, which is genuinely useful for an agent deciding how to handle large diffs. It could go further by saying whether output is truncated or what happens past the limit.

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?

A single compact sentence with the capability front-loaded and the size constraint attached; nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-optional-parameter read tool with full schema coverage and read-only annotations, this is nearly sufficient, and the size limit covers the main operational risk. The absence of any note on output format is a minor gap given there is no output schema.

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 coverage is 100% and both parameters are described in the schema, so the baseline of 3 applies. The description restates the staged concept but adds no format details for the file path or filtering behavior.

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?

States a specific verb and resource ('Read ... Git diffs') and scopes it to unstaged or staged changes, which cleanly separates it from status/log siblings. It does not explicitly name a sibling tool, so it stops short of a 5.

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?

Usage is implied by 'unstaged or staged', which tells the agent the two retrieval modes, but there is no explicit when-to-use versus when-not guidance or reference to alternatives like git_status.

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