Skip to main content
Glama
mergestorm-mcp

mergestorm-mcp

Official

Submit review

review_submit

Submits a local git diff or explicit diff as a Mergestorm review job, returning a job_id immediately so you can poll for completion.

Instructions

Submit a local git diff (or an explicit diff) as a Mergestorm review job. Does not wait by default; returns job_id immediately after submission. Explicit wait: true polls one 45s slice by default. Record job_id and loop review_wait until done. Do not pass 300; hosts drop long MCP calls. On rate_limited, wait retry_after_seconds and inspect or wait for an in-flight review before resubmitting. specialists may be security, performance, architecture, tests, data, api, frontend. governance and seam cannot be requested.

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

Input Schema

NameRequiredDescriptionDefault
cwdNo
baseNo
diffNo
headNo
waitNo
routerNo
threadNo
contextNo
timeout_sNo
specialistsNo
context_filesNo
idempotency_keyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.31

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare non-read-only, open-world, non-idempotent, non-destructive, so the description carries the real behavioral load: non-blocking by default, immediate job_id return, single 45s polling slice under wait: true, host-side dropping of long calls, and rate-limit retry semantics. It stops short of describing what the job result contains or how job_id is scoped, keeping it below 5.

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?

Front-loaded with the core action and default behavior, then workflow, then caveats and parameter notes. The telegraphic phrasing ('Do not pass 300; hosts drop long MCP calls') is dense but purposeful; a little structure would aid scanning, but nothing is wasted.

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?

Covers the async job lifecycle, waiting, rate limiting, and specialist constraints well for a 12-parameter submission tool with no output schema. However, a third of the parameters (router, thread, context, context_files, idempotency_key) have no stated meaning anywhere, which is a meaningful gap for a tool this configurable.

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?

With 0% schema description coverage across 12 parameters, the description compensates for only part of the set: it clarifies diff vs local-diff sourcing, wait, timeout_s (single slice, avoid 300), and specialists (examples plus two forbidden values). Router, thread, context, context_files, idempotency_key, base, head, and cwd are left entirely to the schema, which documents none of them.

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?

States a concrete verb and resource: submit a local git diff (or explicit diff) as a Mergestorm review job. It also distinguishes itself from the sibling workflow by naming review_wait as the polling counterpart, so an agent can tell it apart without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly describes the intended flow (submit, record job_id, loop review_wait), the optional wait: true behavior, a hard warning against passing 300 to timeout_s, and recovery guidance for rate_limited. It also names allowed specialists and states that governance and seam cannot be requested, which is genuine when-not guidance.

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