Skip to main content
Glama

Resolve or reopen review comments

resolve_comments

Marks review comments as resolved or reopens them in a saved review so reviewers see updated status on the page and in review.md. Use after fixing what a comment asked for.

Instructions

Marks review comments as resolved (fixed) or open again, in the saved review. Use it after fixing what a comment asked for, so the reviewer sees the state on the page and in review.md.

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": {
      "reviewId": "<reviewId>",
      "resolved": "<resolved>"
    },
    "name": "resolve_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsNoComment ids to change. Omit to change every comment.
resolvedYestrue marks them resolved (fixed); false reopens them.
reviewIdYesIdentifier returned by start_review.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does well to note the mutation's visible effect on the page and in review.md, and the reversible direction (resolved vs open again) is implied. It says nothing about permissions, what happens with invalid or foreign comment ids, or whether the review must be in a particular state.

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

Conciseness5/5

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

A single tight sentence front-loads the action and follows with the workflow trigger. Every clause earns its place and there is no redundancy with the title beyond an acceptable restatement.

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

Completeness4/5

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

For a three-parameter, fully documented mutation with no output schema, the description covers purpose, timing, and visible side effects adequately. The remaining gap is failure-mode behavior and any precondition on the review's state, which an agent might want before calling.

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 coverage is 100%, so the schema already documents ids, resolved, and reviewId including the 'omit to change every comment' behavior. The description's '(fixed)' gloss on resolved and 'saved review' framing for reviewId only restate that. Baseline 3 applies when the schema does the heavy lifting.

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?

The description gives a specific verb pair and resource: marks review comments resolved or open again, within a saved review. The effect is unambiguous and the scope constraint ('in the saved review') is stated. It does not explicitly contrast with sibling tools like close_review or get_review, so it falls short of full sibling differentiation.

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

Usage Guidelines4/5

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

It states a clear usage context: use it after fixing what a comment asked for, so the reviewer sees the resulting state. That is genuine when-to-use guidance anchored to a workflow moment. It does not state when not to use it or name an alternative tool for related states.

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