Skip to main content
Glama
Sign In
Simple Merge Review MCP

Simple Merge Review MCP

by sigmade
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

show_merge_diff

Display changes between branches to evaluate merge impact. Review file modifications, additions, and deletions.

Instructions

Show changes between branches before merge

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": "show_merge_diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoPathYesPath to the git repository
fromBranchNoBranch to merge from (default: main)main
toBranchNoBranch to merge into (default: current)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description must convey behavioral traits. It implies a read-only operation with 'show' but does not detail output format, side effects, or limitations such as large diffs. Minimal but not misleading.

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?

Description is a single, front-loaded sentence with no wasted words. Efficiently communicates the core purpose.

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

Completeness3/5

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

Given the tool has 3 parameters, no output schema, and no annotations, the description is adequate but could be enhanced with details on what the diff output looks like (e.g., unified diff) or how the default branches work. Not fully complete for an 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?

Schema description coverage is 100% with clear descriptions for each parameter. The tool description adds no extra meaning beyond what the schema provides. Baseline of 3 is appropriate.

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?

Description clearly states verb 'show', resource 'changes between branches', and context 'before merge'. It is specific and distinguishes from siblings: quick_merge_summary likely shows a summary, show_file_diff shows file-level diffs.

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 the description and name, but there is no explicit guidance on when to use this tool versus alternatives like quick_merge_summary or show_file_diff, nor any exclusions or prerequisites.

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