Skip to main content
Glama
Sign In
Simple Merge Review MCP

Simple Merge Review MCP

by sigmade
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

quick_merge_summary

Summarizes file changes and branch status in a Git repository to help you evaluate merge readiness.

Instructions

Quick summary of changes for 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": "quick_merge_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoPathYesPath to the git repository
branchNoBranch to analyze (default: current)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided, so description must disclose behavioral traits. It only says 'summary of changes' without stating whether the tool is read-only, what format the summary is in, or any side effects. This is insufficient for an agent to understand the tool's behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise with one short sentence. It is well-structured and front-loaded, but could benefit from slightly more detail without becoming wordy.

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 no output schema, the description should clarify what the summary contains (e.g., list of files, commit messages) and its format. The tool has 2 parameters and is a summary operation, but the description fails to provide sufficient context for an agent to use it correctly.

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 repoPath and branch. The description adds no extra meaning beyond the schema, so baseline score 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?

The description 'Quick summary of changes for merge' clearly indicates the tool's purpose: it produces a summary of changes related to merging. It effectively differentiates from sibling tools show_file_diff and show_merge_diff, which are likely more detailed diff views.

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?

No explicit guidance on when to use this tool vs siblings. The name 'quick' implies it for overview rather than detailed diffs, but it lacks explicit when-to-use or when-not-to-use statements.

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