Skip to main content
Glama
Sign In
uxloom

uxloom

Official
by uxloom-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

comment_resolve

Resolve a reviewer comment after making the change, and write a real explanation of what was fixed and why. The note persists for the reviewer, and the pin clears in open previews.

Instructions

Resolve a reviewer comment after addressing it. The resolution note is shown to the reviewer and persisted; the pin clears live in every open preview. Never resolve without actually making the change.

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": {
      "id": "<id>",
      "resolution": "<resolution>"
    },
    "name": "comment_resolve"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesComment id
resolutionYesWhat was changed and why — a real sentence the reviewer will read, not an acknowledgment

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.10.0

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations present, the description carries the transparency burden and succeeds: it discloses that the resolution note is shown to the reviewer, is persisted, and clears the pin live in all open previews. These are concrete, observable effects beyond merely stating 'resolve'.

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 concise sentences; the first states the action and precondition, the second adds behavioral consequences and a safety rule. No filler or repetition.

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 simple two-parameter mutation with no output schema, the description provides purpose, precondition, behavioral effects, and a caution. All necessary operational context is present.

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

Parameters4/5

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

Input schema already covers both parameters at 100%, so baseline is 3; the description adds value by explaining that the 'resolution' value is surfaced to the reviewer and persisted, which clarifies the stakes of that parameter. However, it doesn't describe id formatting or any additional constraints beyond the schema.

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?

Description opens with 'Resolve a reviewer comment after addressing it' – a specific verb and target resource that clearly distinguishes it from sibling read/lookup tools like comments_list and comment_context. The phrase 'after addressing it' adds necessary context about the action's precondition.

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?

Provides explicit timing ('after addressing it') and an explicit prohibition ('Never resolve without actually making the change'), which covers both when and when-not to invoke this tool. While no alternative tool is named, the strong operational guardrail clearly differentiates the intended use case from comment listing/context siblings.

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

Deploy Server

Other Tools