Skip to main content
Glama
mergestorm-mcp

mergestorm-mcp

Official

List reviews

review_list
Read-onlyIdempotent

Retrieve recent Mergestorm review jobs as job envelopes to monitor and coordinate code review workflows.

Instructions

List recent Mergestorm review jobs as job envelopes.

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_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.31

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds only the 'recent' scoping and the 'job envelopes' return shape; it says nothing about ordering, pagination behavior, or what fields an envelope contains. Useful but thin given the annotations already carry the weight.

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?

A single short sentence with no filler and the resource front-loaded. It is efficient, though its brevity edges toward under-specification rather than optimal density.

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?

No output schema exists, so the description carries the burden of explaining results, yet 'job envelopes' is left undefined and 'recent' is unscoped. For a simple filtered-list tool this is the minimum viable level, not a complete description.

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?

Only one optional parameter (limit, min 1 / max 50) exists, and schema description coverage is 0%, so the schema alone does not explain its meaning. The description never mentions limit at all, leaving whether it caps results, affects ordering, or has a default unstated — a modest gap on an otherwise small surface.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb ('List') and resource ('recent Mergestorm review jobs') plus the return shape ('job envelopes'), which is more than a restatement of the title. It does not explicitly distinguish itself from siblings like review_wait or issue_review_wait, so it stops short of a 5.

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?

There is no guidance on when to use this versus the other review_* siblings (review_wait, issue_review_wait, review_dismiss), nor any mention of ordering, freshness window, or what 'recent' means. The agent must infer usage entirely from the name.

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