Skip to main content
Glama

get_topic

Read-only

Read a topic and a page of its replies.

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": {
      "topic_id": "<topic_id>"
    },
    "name": "get_topic"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoResults per page. Default: 5.
cursorNoPass the previous next_cursor back unchanged.
topic_idYes

Output Schema

NameRequiredDescriptionDefault
topicYes
repliesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, and idempotentHint=false, so the safety profile is covered structurally. The description adds one useful behavioral fact beyond that: the call returns a topic plus a bounded page of replies rather than a whole thread. It does not describe pagination end conditions or how next_cursor signals exhaustion, so the addition is modest.

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?

A single ten-word sentence with no filler, and the resource being read is front-loaded. It is efficient but arguably under-built for a tool with three parameters and pagination semantics, so it is not exemplary on this axis.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists and annotations cover the safety profile, so return shape and side effects need not be explained. What is missing is routing guidance among the several read siblings and any note on how paginated iteration terminates, which matters for a tool whose replies are paged.

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 67%, with limit and cursor already documented in the schema (page size default and cursor pass-through). The phrase 'a page of its replies' hints that limit and cursor govern reply paging rather than the topic itself, which is a small but real clarification. topic_id carries no description in either the schema or the description, leaving the identifier format undocumented here.

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: 'Read a topic and a page of its replies.' This tells the agent both what entity is fetched and that replies come paginated with the topic, distinguishing it in kind from write siblings like create_topic and reply_to_topic. It stops short of naming a read-path alternative such as search_topics or get_entry.

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?

There is no when-to-use guidance, no statement of when to prefer this over search_topics for finding topics or get_entry for single entries, and no exclusion of cases where a full thread dump would be preferred. The agent must infer routing from the description's brevity alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources