Skip to main content
Glama
Sign In
PerMark

PerMark

by EdelmarSchneider
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

resolve_comment

Idempotent

Mark a comment as done and add a short reply so the person sees what you did. Use the comment id from the list to close out review feedback.

Instructions

Mark one comment done, with a short reply the person reads. The only change an agent can make.

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
idYesComment id from list_comments.
replyNoWhat you did, short.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.7.0
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / id / description
      Previous value: -"The comment's `id`, as `list_comments` gives it."New value: +"Comment id from list_comments."
    • changedInput schema / properties / reply / description
      Previous value: -"A short message to the person saying what you did, such as `Rewritten in 3f2a1c`. They read it under the comment."New value: +"What you did, short."
    • changedInput schema / properties / reply / type
      Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare it as a non-destructive, idempotent write; the description adds two traits not in the annotations — that the reply is read by a person (so the content is user-facing, not a log line) and that this is the sole mutation available in the toolset. It does not state reversibility or what happens to an already-resolved comment.

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 sentences, no filler, with the core action front-loaded and the scoping constraint immediately after. Nothing could be cut without losing information.

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?

For a two-parameter idempotent mutation with annotations and no output schema, the description covers purpose, audience, and scope adequately. Minor gap: it doesn't say what the caller gets back or how the comment's state changes afterward.

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 already documents both parameters (id from list_comments, reply = what you did, short). The description only adds that the reply is read by a person, a marginal gain over the schema; 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?

Names a concrete verb and resource: "Mark one comment done, with a short reply." The second sentence ("The only change an agent can make") distinguishes it from the many read/list siblings without naming them explicitly.

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 only change an agent can make" gives clear context for when this tool is the right choice among twelve largely read-only siblings. It stops short of explicit exclusions, such as when a comment should not be resolved or how to pick among multiple comments.

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