Drop2Run

Reply to a comment

reply_comment

Answers a comment thread on a site as its owner. The reply shows on the page under the owner's name, and the people in the thread are emailed. Publish a fix before replying that it is fixed. The thread stays open unless resolve is true, so the commenter can check and resolve it themselves; resolve only when the person asks. Only the account's owner can reply.

Input Schema

Name	Required	Description
`body`	Yes	The reply, plain text.
`site`	Yes	Subdomain or site id, from list_sites.
`thread`	Yes	Identifier of the thread, from list_comments.
`resolve`	No	Resolve the thread with the reply. False by default.

Output Schema

Name	Required	Description
`id`	Yes	Identifier of the thread, which reply_comment and resolve_comment take.
`url`	Yes	Opens the page at the thread.
`path`	Yes	The page it is on, or the document's path in a documents site.
`quote`	Yes	The words the commenter selected, or the text near a pin; use it to find the source.
`comments`	Yes
`outdated`	Yes	True when it was opened on an earlier version; the words it points at may have changed.
`resolved`	Yes	Whether it is resolved.
`selector`	Yes	The CSS selector of the element it is on.
`resolvedAt`	Yes	When it was resolved, ISO 8601, or null while open.
`resolvedBy`	Yes	Who resolved it, by name, or null while open.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 18, 2026

addedOutput schema / properties / resolvedAt

Added value: +{
+  "description": "When it was resolved, ISO 8601, or null while open.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / resolvedBy

Added value: +{
+  "description": "Who resolved it, by name, or null while open.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "id",
-  "path",
-  "url",
-  "quote",
-  "selector",
-  "outdated",
-  "resolved",
-  "comments"
-]New value: +[
+  "id",
+  "path",
+  "url",
+  "quote",
+  "selector",
+  "outdated",
+  "resolved",
+  "resolvedBy",
+  "resolvedAt",
+  "comments"
+]

First observedOct 14, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations: the reply is publicly visible under the owner's name, thread participants are emailed (an external side effect consistent with openWorldHint), the thread remains open by default, and there is a permission restriction. These are exactly the side effects and constraints an agent needs before invoking a write tool.

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?

Five short sentences, each carrying distinct behavioral or usage information, with the visibility/notification effect stated up front and the resolve policy last. No filler or restatement of the name.

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 write tool with an output schema (so return values need no explanation), the description covers visibility, notification side effects, permissions, and the resolve policy. Nothing an agent needs to call it correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real policy semantics for `resolve` beyond the schema's 'Resolve the thread with the reply': it explains the default behavior (thread stays open) and the condition under which resolving is appropriate. `site` and `thread` provenance is already covered by the schema.

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+resource ('Answers a comment thread on a site as its owner') and clarifies the acting identity. It implicitly differentiates from siblings like resolve_comment and reopen_comment by explaining that the thread stays open unless `resolve` is true, though it never names those alternatives explicitly.

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?

Gives explicit when/when-not guidance: publish the fix before replying that it is fixed, and resolve only when the commenter asks. It also states the precondition that only the account owner can reply, so an agent can decide before calling whether it is allowed to act.

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

All Drop2Run tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.