Skip to main content
Glama
Sign In
Easel

Easel

by nemodleo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

resolve_comment

Marks a design comment as resolved after you apply its requested fix, or reopens it by setting resolved to false.

Instructions

Mark a comment as resolved (pass resolved=false to reopen it). Use it after fixing what a comment asked for.

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

Input Schema

NameRequiredDescriptionDefault
idYes
resolvedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the operation is reversible via resolved=false and implies a workflow precondition, but it does not mention permissions, error behavior when the ID is invalid, idempotency, or what the tool returns.

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?

Two short sentences, front-loaded with the core action. Every clause adds usable information, including the reopen behavior and intended timing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple mutation tool with no annotations, no output schema, and 0% schema description coverage, the description covers the core action and reversal semantics but leaves gaps around permissions, invalid IDs, and return behavior.

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 0%, so the description must compensate. It adds important meaning for the resolved parameter (pass false to reopen), but does not explain the required id parameter beyond the obvious name.

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?

The description states a specific verb and resource: 'Mark a comment as resolved'. It also clarifies the inverse state ('reopen it'), which makes the tool clearly distinct from siblings like add_comment, reply_comment, and list_comments.

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?

It gives explicit usage timing: 'Use it after fixing what a comment asked for.' It also explains the reopen case, though it does not name alternative tools or state when not to use it.

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