Skip to main content
Glama
mergestorm-mcp

mergestorm-mcp

Official

Stop Vortex review

review_stop_pr
DestructiveIdempotent

Cancel the Vortex review running on a pull request. Reports when no review is active instead of starting a new one.

Instructions

Cancel the Vortex review running on a pull request. Starts nothing; says so when no review is running.

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": {
      "owner": "<owner>",
      "repo": "<repo>",
      "pr_number": "<pr_number>"
    },
    "name": "review_stop_pr"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYes
ownerYes
pr_numberYes

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 destructive=true, idempotent=true, and readOnly=false, so the mutation profile is covered. The description adds a genuinely useful no-op disclosure ('says so when no review is running'), but it does not say what happens to a partially completed review or its results, nor whether special permissions are needed.

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?

Two short sentences with the action front-loaded and no filler. The second clause is terse to the point of being slightly cryptic in phrasing, 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?

For a destructive three-parameter mutation with no output schema, the description covers the core action and the no-review edge case. It stops short of describing return behavior or side effects on an in-flight review, which matters given destructiveHint=true.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three required parameters, so the description carries the burden of explaining owner, repo, and pr_number. It says nothing about them; the only mitigation is that the names follow conventional pull-request conventions and are largely self-describing.

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 specific verb ('Cancel') and a specific resource ('the Vortex review running on a pull request'), so the agent knows exactly what operation is performed. It implicitly contrasts with the start tool via 'Starts nothing' but does not name any sibling explicitly.

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?

The phrase 'Starts nothing' implies this is not a way to kick off a review and the caller should use a start tool for that, which is useful routing context. However, there is no explicit when-to-use/when-not guidance relative to siblings like review_wait_pr or review_dismiss, leaving the agent to infer the boundary.

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