Skip to main content
Glama
Sign In
mcgl-mcp

mcgl-mcp

by exi66
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Topic page

forum_get_topic
Read-only

Retrieves posts from a forum topic, returning the newest page by default or a specified page with post details, pagination totals, and topic metadata such as polls and notices.

Instructions

Posts of a topic. Without page: the newest pageSize posts (latest:true) - usually what is needed. With page: pages counted from the topic start, pageSize posts each (default 15); the page holding post #N is ceil(N/pageSize). Post numbers (#N) are continuous. Returns title, section, totalPages, totalPosts, posts (number, id, author, postedAt, text, rating; deleted posts are {deleted:true}). The latest view and page 1 also include poll (if any), notices (e.g. 'moved from section') and current readers. author.accountDeleted: account removed or banned. Post text markup: [quote: nick]..[/quote], [spoiler: title]..[/spoiler], [image: url], [video: url], [audio: url], [Item name #id] or [item #id] (#id:meta for variants), [craft] grid of item ids with a legend. Boolean flags appear only when true.

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": {
      "topicId": "<topicId>"
    },
    "name": "forum_get_topic"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page from the topic start; omit for the newest posts
topicIdYes
pageSizeNoPosts per page

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0-dev

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses exactly what comes back: title, section, totalPages, totalPosts, post fields, the {deleted:true} shape for removed posts, and that poll/notices/readers appear only on the latest view or page 1. It also documents author.accountDeleted semantics and the convention that boolean flags appear only when true, which the agent cannot infer from annotations.

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?

Front-loaded with purpose, then the page/omit-page rule, then return shape, then the markup legend — a logical progression where nearly every sentence carries operational detail. The markup inventory is long and dense, but it is the only place that decoding information exists (no output schema), so it earns its space.

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

Completeness5/5

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

With no output schema, the description fully carries the burden of describing returns, page-1-only fields, and post text encoding, including the [quote], [spoiler], [image], and item-reference markup patterns. Nothing an agent needs to call the tool or interpret its output is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema covers 67% of parameters, but the description adds real meaning: page is 1-based from the topic start, pageSize defaults to 15 and is uniform across pages, and it supplies the ceil(N/pageSize) formula for locating the page holding a given post number. The note that post numbers are continuous further disambiguates page addressing.

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?

"Posts of a topic" names the resource and, together with the pagination explanation, makes clear this retrieves the post collection rather than a single post (forum_get_post) or a topic list (forum_latest_topics). The opening is a noun fragment rather than an explicit verb, which slightly weakens it, but the scope is unambiguous.

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

Usage Guidelines4/5

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

It gives explicit mode-selection guidance: omitting page returns the newest posts and is "usually what is needed," while supplying page walks from the topic start. It does not name sibling alternatives or say when-not to use this tool, but the within-tool branching rule is stated clearly.

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