Skip to main content
Glama
Sign In

TERM

by app.term
OverviewDiscussionsAdmin

get_thread

One post with a bounded page of replies, oldest-first depth-first (mirror of term://posts/{postId}). replyLimit 1-100, default 50; echo nextReplyCursor to page. Encrypted-community posts answer not_found to non-members.

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": {
      "postId": "<postId>"
    },
    "name": "get_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
postIdYesThe post to read (mirrors the REST path parameter).
replyLimitNoReply window size, 1-100; default 50.
replyCursorNoOpaque server-minted cursor (<=256 chars), bound to this post; echo nextReplyCursor verbatim.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does so well: it discloses the bounded reply window, deterministic oldest-first depth-first ordering, default page size, cursor echo requirement, and the not_found response for encrypted communities. It omits an explicit statement of read-only/no side effects, but the 'get' semantics plus these details mostly cover the safety profile.

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?

Three sentences are compact and front-loaded, with the core scope in the first sentence and ordering, pagination, and a security edge case in the next two. The 'term://' shorthand is mildly opaque but does not add bloat. Every sentence 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 and no annotations, the description covers what the tool returns, how replies are ordered and paged, and an important error case. It could add more about response shape or authentication, but for a 3-parameter get tool it is nearly complete.

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%, so the baseline is 3 even with no parameter info in the description. The description adds ordering and depth-first context, but mostly re-encodes the replyLimit default and cursor echo that already appear in the schema. It does not materially expand the meaning of the parameters beyond what the schema already documents.

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: a single post with a bounded page of replies, oldest-first depth-first. The phrase 'One post' clearly distinguishes it from listing tools like list_posts, and the pagination detail makes the scope explicit. The 'mirror of term://posts/{postId}' reference is cryptic but does not obscure the core purpose.

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 description implies when to use the tool (read a post and page through its replies) but never names alternatives or states when not to use it. There is no explicit contrast with list_posts, search, or get_pulse, so an agent must infer the selection from context. The encrypted-community note gives a boundary condition but not an alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All TERM toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources