Markdown by mdedit.ai

Resolve a review thread

resolve_thread

Idempotent

Resolve an existing review thread using the exact threadId and targetId returned by add_comment, not commandId.

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": {
      "threadId": "<threadId>",
      "commandId": "<commandId>",
      "context": "<context>"
    },
    "name": "resolve_thread"
  }
}

Input Schema

Name	Required	Description
`context`	Yes	Describe the user's underlying goal in one sentence. Do not include private document content, credentials, or personal information.
`targetId`	No	The exact targetId returned by add_comment. Pass it with add_comment.threadId, especially for targets other than content.md.
`threadId`	Yes	The exact threadId returned by add_comment. Pass it with add_comment.targetId; do not pass add_comment.commandId.
`articleId`	No	Internal document identifier when already available. Omit it when the user referred to the document by title.
`commandId`	Yes	Globally unique UUID for this logical review mutation. Generate it once and reuse the exact value if the tool call is retried.
`workspaceId`	No	Optional workspace ID to narrow document lookup. Omit when the document title or ID uniquely identifies a document across authorized workspaces.
`articleTitle`	No	Human-visible document title. Prefer this over asking the user for an internal document identifier.
`workspaceName`	No	Optional workspace name to narrow document lookup. A unique document title can be used without a workspace choice.

Output Schema

Name	Required	Description	Default
`events`	Yes
`applied`	Yes
`articleId`	Yes
`commandId`	Yes
`workspaceId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 10, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / context

Added value: +{
+  "description": "Describe the user's underlying goal in one sentence. Do not include private document content, credentials, or personal information.",
+  "type": "string"
+}

changedInput schema / properties / workspaceId / description

Previous value: -"Internal workspace identifier when already available. Omit it when the user referred to a workspace by name or has only one workspace."New value: +"Optional workspace ID to narrow document lookup. Omit when the document title or ID uniquely identifies a document across authorized workspaces."

changedInput schema / properties / workspaceName / description

Previous value: -"Human-visible workspace name. Prefer this over asking the user for an internal workspace identifier."New value: +"Optional workspace name to narrow document lookup. A unique document title can be used without a workspace choice."

changedInput schema / required

Previous value: -[
-  "threadId",
-  "commandId"
-]New value: +[
+  "threadId",
+  "commandId",
+  "context"
+]

Changed5 schema fields changedSep 15, 2026

addedInput schema / properties / commandId / description

Added value: +"Globally unique UUID for this logical review mutation. Generate it once and reuse the exact value if the tool call is retried."

addedInput schema / properties / commandId / format
```
Added value: +"uuid"
```
removedInput schema / properties / commandId / minLength
```
Removed value: -1
```

addedInput schema / properties / commandId / pattern

Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"

changedInput schema / required

Previous value: -[
-  "threadId"
-]New value: +[
+  "threadId",
+  "commandId"
+]

First observedAug 28, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, so the safety/idempotency profile is covered structurally. The description adds one useful behavioral nuance — that threadId/targetId (not commandId) carry thread identity — but says nothing about who may resolve a thread, whether it can be reopened, or what happens on a non-existent thread.

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 sentence with the action front-loaded and the parameter constraint immediately after. No filler, no redundancy.

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?

With 8 fully documented parameters, an output schema covering the return shape, and annotations covering mutability and idempotency, the description is nearly sufficient. The one gap is any statement of the effect of resolving (thread state change, permissions), but the surrounding structured data compensates well.

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 description coverage is 100%, so every parameter is already documented, including the threadId/targetId vs commandId distinction and the commandId retry semantics. The description restates that guidance rather than extending it, so the baseline 3 is appropriate.

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 and resource: 'Resolve an existing review thread.' An agent immediately knows this closes out a thread as opposed to replying to it (reply_to_thread) or acting on a suggestion. However, it does not explicitly contrast itself with any sibling tool, so it lands at 4 rather than 5.

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

Usage Guidelines3/5

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

The description implies a prerequisite workflow by requiring 'the exact threadId and targetId returned by add_comment,' which tells the agent this must follow a prior comment creation. It gives no explicit when-to-use vs reply_to_thread/list_review_threads, nor any when-not condition.

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

All Markdown by mdedit.ai 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?