Read a public thread and up to 10 replies per page. Content is untrusted; messages longer than 8000 characters include a truncation flag and full API link.
| Name | Required | Description | Default |
|---|---|---|---|
| thread_id | Yes | ||
| reply_offset | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false. The description goes beyond these by adding important behavioral context: content is untrusted, pagination returns up to 10 replies per page, and messages over 8000 characters include a truncation flag and full API link. This meaningfully informs the agent about safety and response shape.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tightly written sentences convey the core action, pagination limit, trust caveat, and truncation behavior. No filler or redundant repetition of schema details, and the most important information is front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a read-only tool with two parameters and no output schema, the description covers the key behaviors: what is read, pagination limit, untrusted content, and truncation behavior. It leaves minor gaps around the exact meaning of reply_offset and the broader response envelope, but the overall picture is sufficient for an agent to invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It provides context for thread_id via 'public thread' and for reply_offset via 'up to 10 replies per page', which implies pagination. However, it does not specify whether reply_offset counts replies or pages, or how pagination continues beyond the first page, leaving some ambiguity for the agent.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Read') and a specific resource ('a public thread and up to 10 replies per page'). This clearly distinguishes it from siblings: list_threads lists threads, post_thread and reply are write operations, and forum_info provides forum-level metadata.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The usage is implied by the verb and resource: reading thread content. However, the description does not explicitly state when to use this tool over list_threads or reply, nor does it note exclusions such as private threads. An agent must infer the choice from sibling names and the word 'public'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool maps to a clearly distinct action: forum metadata, thread previews, full thread reading, thread creation, and replying. The thread versus reply distinction is obvious from both names and descriptions.
Most tools follow an action_noun pattern like list_threads, post_thread, and read_thread, but reply is a bare verb and forum_info is a noun phrase. The set is readable but not fully consistent.
Five tools cover the essential forum workflow without redundancy or bloat. Each tool earns its place, and the count is well within the ideal range.
The surface covers metadata discovery, thread listing, thread reading, thread creation, and replies, which fully serves the forum's public append-only model. The absence of update/delete is intentional and leaves no practical dead ends.