Skip to main content
Glama
Sign In

Soleil Clusters

by com.soleilpictures
OverviewDiscussionsAdmin

Resolve comments

resolve_comments
DestructiveIdempotent

CHANGES whether comment threads on a board are resolved: resolved true (default) puts them away, false reopens them. Takes thread ids from list_comments. On the canvas a thread's author or an editor may resolve it; inside docs and notes, an editor. Resolve only what the person asked.

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": {
      "board_id": "<board_id>",
      "comment_ids": "<comment_ids>"
    },
    "name": "resolve_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
board_idYesThe board
resolvedNotrue (default) resolves; false reopens
comment_idsYesThread ids from list_comments

Output Schema

NameRequiredDescriptionDefault
changedNo
refusedNo
board_idNo
resolvedNo
not_foundNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial behavior beyond annotations: the per-context permission model (thread author or editor on canvas; editor-only in docs and notes) and the default of resolved=true. It also clarifies reversibility (false reopens), which contextualizes the destructiveHint=true annotation rather than contradicting it.

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?

Front-loads the mutation and its two directions, then provenance, then permissions, then the scope caution. Four tight sentences with no redundancy.

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?

With annotations covering safety hints and an output schema covering return values, the description fills the remaining gaps an agent needs: permissions per context, default behavior, and where ids originate.

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 the schema already documents board_id, resolved default, and the comment_ids source, so the description largely restates it. The one added detail is the provenance chain for ids, which is useful but marginal; 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?

States a specific verb and resource — changes whether comment threads on a board are resolved — and immediately explains the bidirectional effect (true puts them away, false reopens). It also names the sibling that supplies the ids (list_comments), so an agent can place it relative to the read-side tool without opening schemas.

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?

Gives clear operational context: ids come from list_comments, and the caution 'Resolve only what the person asked' bounds scope. When-to-use is implied rather than contrasted with an explicit alternative, but no plausible competing tool is misidentified.

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

All Soleil Clusters 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