Skip to main content
Glama
Sign In
criticmarkup

criticmarkup

by Martennnnn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

reply_to_comment

Reply to an existing discussion thread using its 4-character UID, even when line cutoffs apply, to keep review conversations organized.

Instructions

Replies to an existing discussion thread by its 4-character UID (e.g. 'o1b7'). Unaffected by the line cutoff.

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": {
      "filepath": "<filepath>",
      "thread_id": "<thread_id>",
      "reply_text": "<reply_text>"
    },
    "name": "reply_to_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
filepathYes
thread_idYes
reply_textYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the whole behavioral burden. It does disclose that this is a write against an existing thread and adds a non-obvious trait ('Unaffected by the line cutoff'), but that phrase is unexplained, and nothing is said about permissions, whether the reply is immediately visible, or what happens with a stale or invalid thread ID.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the core action and zero filler. The trailing cutoff sentence is terse to the point of being cryptic without surrounding context, but nothing is wasted.

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?

Return values are covered by the existing output schema and the thread ID format is illustrated, so the main gaps are the meaning of filepath and failure behavior for a missing thread. For a three-parameter tool this is close to complete, though not fully.

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 0%, so the description must compensate. It does well for thread_id (4-character UID with a concrete example 'o1b7'), but filepath is left ambiguous (which file contains the discussion?) and reply_text is passed without noting formatting or length constraints, leaving two of three parameters under-specified.

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: 'Replies to an existing discussion thread'. The 'existing thread' phrasing implicitly distinguishes it from write_comment, which creates a new thread, though no sibling is named explicitly.

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 requirement of an already-existing thread is implied by 'existing discussion thread' and the thread_id parameter, but the description never says when to prefer this over write_comment or what to do if the thread ID is unknown. Usage is inferable rather than stated.

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