Skip to main content
Glama
Sign In
Simple Merge Review MCP

Simple Merge Review MCP

by sigmade
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

show_file_diff

Compare changes in a specific file between two git branches to view exact differences.

Instructions

Show specific changes in a file between branches

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>",
      "filename": "<filename>"
    },
    "name": "show_file_diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoPathYesPath to the git repository
filenameYesPath to the file relative to the repository root
fromBranchNoBranch to compare from (default: main/master)
toBranchNoBranch to compare to (default: current)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, and the description lacks behavioral details such as output format, whether it runs git diff, or prerequisites like a clean working directory. Minimal transparency beyond purpose.

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 sentence that is concise and front-loaded with the core action. No wasted words.

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?

With no output schema, the description should explain the return value (e.g., a text diff). It only says 'show changes,' leaving ambiguity. Sibling tools exist but no comparative completeness.

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 description coverage is 100%, so the schema already documents each parameter. The description adds no additional meaning beyond what the schema provides, resulting in baseline score.

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 shows specific changes in a file between branches, with a specific verb and resource. It distinguishes from siblings like quick_merge_summary and show_merge_diff, which focus on merge summaries and diffs.

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?

No guidance on when to use this tool versus alternatives like show_merge_diff. The description implies usage for a single file diff between branches but provides no when-not-to-use or context.

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