Skip to main content
Glama
Sign In

PubSpace

by ai.pubspace
OverviewDiscussionsAdmin
This connector has been deprecated

Duplicate - user other one published

Resolve a comment thread

resolve_comment
Idempotent

Mark a comment thread resolved (or reopen it with resolved: false) after you have addressed it. The pin turns grey and drops out of the open list for everyone; nothing is deleted. Returns { ok, page_id, thread_id, resolved }. Fails with thread_not_found if the id is not an open-or-resolved thread on that page.

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": {
      "page_id": "<page_id>",
      "thread_id": "<thread_id>"
    },
    "name": "resolve_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idYesThe page id: the `id` field from publish_page or list_pages (also the last path segment of the page URL, …/docs/<page_id>). Only pages in the connected maker's space are visible.
resolvedNoDefault true. false reopens the thread.
thread_idYesA thread `id` from list_comments.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, it discloses the visible side effect (the pin turns grey and drops out of the open list for everyone), explicitly reassures that nothing is deleted, gives the exact return payload { ok, page_id, thread_id, resolved }, and names the failure mode thread_not_found with the condition that triggers it. This is unusually rich behavioral context for a mutation 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?

Three tight sentences ordered as action, effect, return value, error. Every sentence carries distinct information and the primary action is front-loaded with no filler.

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?

Although no output schema exists, the description inlines the return shape, so an agent knows what comes back. Combined with the error case and the side-effect scope, nothing needed to call this correctly or interpret the result 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 meaning: it reinforces the resolved: false inversion as a reopen and constrains thread_id to an open-or-resolved thread on that page via the thread_not_found rule. The page_id scoping caveat lives in the schema rather than the description, so it is not a full 5.

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?

"Mark a comment thread resolved (or reopen it with resolved: false)" gives a specific verb plus resource and covers both directions of the operation. It is clearly distinct from the sibling comment tools (list_comments, set_comments) and from page-level tools, so an agent can select it without opening the schema.

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?

The phrase "after you have addressed it" states the precondition for calling, and "resolved: false" states when to use the reverse mode. It stops short of naming an alternative tool (e.g. list_comments to find the thread first) or describing when not to resolve, so it is clear but not fully exhaustive.

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

All PubSpace toolsInspect
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