Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

Topic Replies

topic_replies
Read-onlyIdempotent

Retrieve paginated replies to a discussion topic. Specify topic ID and optional page/size parameters to fetch replies efficiently.

Instructions

Get replies to a discussion topic, paginated (page default 1, size default 20, range 1-50)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_jqNoOptional jq filter (jaq syntax) applied to this tool's JSON response before it is returned; it never changes the upstream request. One output is returned as-is, several as a JSON array, none as []. Module imports and the `env`/`debug`/`stderr` builtins are unavailable. Example: .data | map({symbol}). Omit for the full response.
pageNoPage number, 1-based (default: 1).
sizeNoRecords per page, 1-50 (default: 20).
topic_idYesTopic ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.12.0
    • addedInput schema / properties / _jq / description
      Added value: +"Optional jq filter (jaq syntax) applied to this tool's JSON response before it is returned; it never changes the upstream request. One output is returned as-is, several as a JSON array, none as []. Module imports and the `env`/`debug`/`stderr` builtins are unavailable. Example: .data | map({symbol}). Omit for the full response."
    • removedInput schema / properties / page / format
      Removed value: -"int32"
    • removedInput schema / properties / size / format
      Removed value: -"int32"
  2. Changed1 schema field changedv0.10.6
    • addedInput schema / properties / _jq
      Added value: +{
+  "type": "string"
+}
  3. Changed2 schema fields changedv0.10.0
    • changedInput schema / properties / page / default
      Previous value: -nullNew value: +1
    • changedInput schema / properties / size / default
      Previous value: -nullNew value: +20
  4. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"TopicRepliesParam"
  5. Addedv0.4.5
  6. Removedv0.4.0
  7. Addedv0.3.2
  8. Removedv0.3.1
  9. First observedv0.1.12

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description need not restate. It adds concrete pagination behavior (defaults and limits), which is useful beyond annotations.

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?

Single sentence, front-loaded with purpose and pagination details. No fluff; every word earns its place.

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?

Given no output schema, the description doesn't explain return structure, but annotations cover safety and schema covers parameters. It omits potential edge cases (e.g., empty replies), but for a simple read tool this is sufficient.

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 covers 100% of parameters with descriptions (e.g., page default, size range). The description restates these but adds no new semantics beyond 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?

Clear verb ('get') and resource ('replies to a discussion topic'), with pagination details. It distinguishes from siblings like 'topic_create_reply' (write) and 'topic'/'topic_detail' (topic itself), though it doesn't explicitly name them.

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?

Implies usage when needing replies for a topic, and pagination details hint at when to adjust parameters. No explicit 'use instead of X' guidance, but sibling tools like 'topic_create_reply' suggest a clear separation (read vs. write).

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