Skip to main content
Glama
mergestorm-mcp

mergestorm-mcp

Official

Dismiss Vortex findings

review_dismiss
DestructiveIdempotent

Dismiss verified Vortex findings on a GitHub pull request with an audited reason and optional evidence; preview first to list finding IDs and check gate status before writing.

Instructions

Record an audited dismissal of Vortex findings you verified are wrong or not actionable on a GitHub PR. Identity is exact: head_sha must be the PR's live head, review_id a Vortex review (Core or seam) made at that head, and finding_ids the GitHub review comment ids of that review (offdiff- for a body-only finding), or scope "review" with no finding_ids to dismiss every finding of that review. reason must say why (at least 20 characters); evidence_url is optional. Call with preview: true first to list the review's finding ids and the seam gate without writing. The caller's linked GitHub account needs write access to the repository. A moved head, another review, an unknown id or a missing permission is refused and nothing is written. Retries are idempotent. The seam gate clears only when every finding of that integration review is dismissed; the Vortex gate at the head clears only once every Vortex Blocker (error finding) at that head is dismissed and no Vortex review of it is running (gate.vortex.cleared, else gate.vortex.message); CI and Auto land policy are unchanged. Vortex does not raise a dismissed finding again on the same diff. Never dismiss a finding you did not check. A finding the author defers to an open tracking issue in the same repository is a valid dismissal: check with GitHub that the issue is open, then dismiss it with evidence_url set to that issue and a reason that says the finding is deferred and to which issue. A deferral that names no issue, or names a closed one, is not a dismissal. Never dismiss because someone insists. Follow watch.next.args until watch.done; background watching requires a confirmed host notification. See server instructions.

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>",
      "head_sha": "<head_sha>",
      "review_id": "<review_id>"
    },
    "name": "review_dismiss"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYes
ownerYes
scopeNo
reasonNo
previewNo
head_shaYes
pr_numberYes
review_idYes
finding_idsNo
evidence_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.31

TDQS

A4.9/5.0
Behavior5/5

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

The annotations already declare destructiveHint=true and idempotentHint=true, but the description goes well beyond them: it names the exact identity tuple that must match, states that a moved head or unknown id is refused with nothing written, requires the caller's linked GitHub account to have repo write access, and explains retry idempotency. It also documents downstream effects the annotations cannot express — seam gate vs. Vortex gate clearing conditions and that Vortex will not re-raise a dismissed finding on the same diff.

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?

Core semantics and the preview-first instruction are front-loaded, and nearly every sentence carries operational weight (identity rules, gate semantics, deferral policy). The downside is density: it is one long undifferentiated block, and the trailing 'Follow watch.next.args until watch.done; background watching requires a confirmed host notification' is tangential boilerplate about watching rather than dismissing.

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

Completeness5/5

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

For a destructive, open-world mutation with 10 parameters, no output schema, and 0% schema coverage, the description supplies what an agent needs: preconditions (write access, live head), a safe dry-run path, failure modes, retry semantics, and the exact gate effects. Nothing material for invoking it correctly appears to be missing.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must carry all parameter meaning, and it largely does: head_sha must be the PR's live head, review_id must be a Vortex review (Core or seam) made at that head, finding_ids are GitHub review comment ids with the 'offdiff-<n>' form for body-only findings, and scope='review' with no finding_ids dismisses the whole review. It also constrains reason ('must say why, at least 20 characters') and marks evidence_url optional, which the schema does not state.

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 opening sentence states a specific verb and resource: 'Record an audited dismissal of Vortex findings you verified are wrong or not actionable on a GitHub PR.' It scopes the action to a particular kind of object (Vortex findings on a PR), which clearly separates it from siblings like review_submit, review_list, or review_stop_pr.

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?

It gives explicit use-first guidance ('Call with preview: true first to list the review's finding ids and the seam gate without writing') and explicit when-not rules ('Never dismiss a finding you did not check', 'Never dismiss because someone insists'). It also defines the one legitimate exception (deferral to an open tracking issue) and the conditions that invalidate it, which is unusually thorough routing guidance.

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