Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_comment_thread

Read-only

Retrieve a complete comment thread—the root comment and all replies in oldest-first order—by thread ID to review design feedback in context.

Instructions

Retrieve a whole thread (root + replies) ordered oldest-first.

Free door, tiered answer — Free: On the designs you keep · Pro: ✓ · Business: ✓ · Enterprise: ✓.

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

Input Schema

NameRequiredDescriptionDefault
thread_idYesThe thread's id: the ``thread_id`` on any of its comments (a root comment's own ``comment_id``).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / thread_id / description
      Added value: +"The thread's id: the ``thread_id`` on any of its comments (a root comment's own ``comment_id``)."
  2. Addedv1.5.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare a safe read (readOnlyHint=true, destructiveHint=false, openWorldHint=false). The description adds genuinely useful behavior beyond that: the result includes replies and is sorted oldest-first. However, the tier line ('Free door, tiered answer — Free: On the designs you keep · Pro: ✓ ...') is garbled boilerplate that adds noise rather than telling the agent whether this call is gated or what happens when it is.

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

Conciseness3/5

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

The first sentence is tight and front-loaded. The second sentence is opaque marketing boilerplate that an agent cannot parse into an actionable constraint, costing efficiency without adding clarity.

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?

One required parameter, fully documented in the schema, a clear read-only annotation set, and the description covers scope and ordering — enough to call it correctly. It is short of ideal only because it never mentions the comment-list sibling or what the thread payload roughly contains.

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 100% and the thread_id property already explains that a root comment's own comment_id is a valid id. The description adds nothing about the parameter, so baseline 3 applies.

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?

The first sentence gives a specific verb and resource (retrieve a whole thread) plus the scope (root + replies) and ordering (oldest-first), which an agent can act on. It does not distinguish itself from the nearby sibling list_mesh_comments, which is the most likely confusion point.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No statement of when to call this versus list_mesh_comments, reply_to_comment, resolve_comment_thread, or reopen_comment_thread. The only conditional text is a tier-availability line, not a usage rule.

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