Rollstack

Resolve comment thread

resolveReportComment

Idempotent

Resolves a comment thread once what it asked for is done, or opens it again, as the user. Only a thread's first comment can be resolved. Members who can comment on the report may.

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": {
      "params": "<params>",
      "body": "<body>"
    },
    "name": "resolveReportComment"
  }
}

Input Schema

Name	Required	Description
`body`	Yes
`params`	Yes
`idempotencyKey`	No	A unique value, such as a UUID, that makes retrying this call safe. A retry with the same key within 24 hours answers the first call's result instead of running it again. Use a new key for each new call. From 1 to 255 printable ASCII characters.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false), the description discloses that the change is attributed to the acting user, requires comment-level permission, is reversible, and is restricted to a thread's first comment. That is real behavioral value the annotations don't carry; only rate limits or side effects on notifications are unstated.

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?

Two tight sentences, front-loaded with the primary action and followed by the two scoping constraints. Nothing is wasted and no sentence restates the name or title.

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 mutation tool with no output schema, the description covers the trigger, the permission model, attribution, reversibility, and the first-comment restriction. What an agent still lacks is any statement of what the call returns, which matters little for a boolean toggle but is the remaining gap.

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?

The schema already documents id, commentId, resolved, and idempotencyKey in detail, so the description needn't repeat them. Its one contribution is the constraint that only a thread's first comment can be resolved, which reinforces which commentId is valid, but it adds no syntax or format detail of its own.

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 (resolves / opens again) on a specific resource (comment thread), and the reversible nature is explicit. It doesn't name a sibling like listReportComments or createReportComment, so the differentiation is by implication rather than by explicit contrast.

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?

"once what it asked for is done" gives a clear trigger condition to resolve, and "opens it again" covers the inverse case. Permission guidance ("Members who can comment on the report may") is included. It stops short of naming an alternative for reading threads or how to locate the thread, though the schema covers that.

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

All Rollstack tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?