Skip to main content
Glama
Sign In
drop2run-mcp

drop2run-mcp

Official
by Drop-to-run
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Resolve a comment thread

resolve_comment
Idempotent

Marks a comment thread as resolved for the site owner, moving it from open to resolved on the current version. Use when the person asks; otherwise let the commenter confirm the fix.

Instructions

Marks a comment thread on a site resolved, as its owner. It moves from the open threads to the resolved ones of the version the site serves now. Resolve when the person asks; otherwise leave it for the commenter to confirm the fix. reopen_comment undoes it.

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": {
      "site": "<site>",
      "thread": "<thread>"
    },
    "name": "resolve_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSubdomain or site id, from list_sites.
threadYesIdentifier of the thread, from list_comments.

Output Schema

NameRequiredDescriptionDefault
idYesIdentifier of the thread, which reply_comment and resolve_comment take.
urlYesOpens the page at the thread.
pathYesThe page it is on, or the document's path in a documents site.
quoteYesThe words the commenter selected, or the text near a pin; use it to find the source.
commentsYes
outdatedYesTrue when it was opened on an earlier version; the words it points at may have changed.
resolvedYesWhether it is resolved.
selectorYesThe CSS selector of the element it is on.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.5

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly=false, idempotent=true, destructive=false, openWorld=true, so the safety profile is covered. The description adds real behavioral context: the thread moves from open to resolved in 'the version the site serves now', and the action is performed as the thread owner. It does not state explicit permission requirements beyond the ownership hint, keeping it just short of a 5.

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?

Three short sentences, zero filler, with the core action and state transition front-loaded and the routing guidance following. Every sentence earns its place.

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?

An output schema exists, so return values need no explanation. The description covers what changes, the version scoping, and the reversal path; only the precise authorization model ('as its owner') is somewhat implicit.

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% and both parameters already name their source tools (list_sites, list_comments) in the schema. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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?

Specific verb+resource ('Marks a comment thread on a site resolved') with the actor qualifier ('as its owner') and the resulting state transition. It is clearly distinguishable from siblings reply_comment and reopen_comment.

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?

'Resolve when the person asks; otherwise leave it for the commenter to confirm the fix' gives an explicit when-to-use and when-not-to-use condition, and 'reopen_comment undoes it' names the reversal alternative. Nothing is left to inference.

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