Show the diff for a specific file or all changed files. Returns unified diff text.
| Name | Required | Description | Default |
|---|---|---|---|
| staged | No | Show staged diff. Default false. | |
| filePath | No | Repo-relative file path. If empty, shows all. | |
| workingDirectory | No | Git repo path. Default current directory. | . |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description only says shows diff and returns text. Lacks details on handling binary files, no-changes cases, or authentication/authorization needs. Minimal but not contradictory.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single concise sentence front-loading purpose and output format. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema and 3 simple params, description is adequate but misses broader context like requiring a git repository and behavior differences for staged vs unstaged diffs.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema covers 100% of parameters; description adds no extra meaning beyond 'specific file or all changed files' which is already evident from filePath default.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the tool shows diffs for a specific file or all files, returning unified diff text. It distinguishes itself from siblings like find_changes or show_history by focusing on diff output.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives like find_changes or get_updates. Missing prerequisites (e.g., git repo) and exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.