Skip to main content
Glama
Sign In
mcgl-mcp

mcgl-mcp

by exi66
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Section topics

forum_list_topics
Read-only

Lists topics in a Minecraft Galaxy forum section, with pinned threads first then by last activity, showing reply permissions, page counts, and authors. Use it to browse a section's discussions.

Instructions

Topics of one section, pinned first, then by last activity. Section ids come from forum_list_sections. Topic fields: pinned; closed (title struck through on the forum, no replies allowed); whoCanReply: all | vip | premium_platinum | moderators (only visible in topic lists, not on the topic page); pages (topic page count); created/last: author and time. 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": {
      "sectionId": "<sectionId>"
    },
    "name": "forum_list_topics"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number
sectionIdYesSection id, 1-11

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0-dev

TDQS

A4/5.0
Behavior4/5

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

With readOnlyHint/openWorldHint already covering the safety profile, the description adds real value: result ordering, sparse booleans ('appear only when true'), what 'closed' means operationally, and that whoCanReply is visible only in lists. It does not discuss list size or pagination behavior beyond what the schema states.

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?

It is front-loaded with the primary fact (what the list is and its ordering) before field details, and every clause carries information. The semicolon-separated field list is dense but justified given there is no output schema.

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?

With no output schema, the description does much of the return-value documentation itself (pinned, closed, whoCanReply, pages, created/last). Minor gaps remain on list page size and total counts, but an agent can call this correctly with what is provided.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3; the description earns above baseline by documenting where sectionId values come from (forum_list_sections), which the schema does not say. The page parameter's meaning is left entirely to the schema.

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?

The description names the resource and its scope precisely (topics of a single section) plus the ordering rule (pinned first, then last activity), which implicitly separates it from forum_latest_topics and forum_get_topic. It lacks an explicit 'unlike X, use Y' contrast, so it falls just short of 5.

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 supplies a concrete prerequisite/route ('Section ids come from forum_list_sections'), which tells the agent it must call the sections tool first. It does not state when to prefer forum_latest_topics over this tool, so there is no explicit alternative guidance.

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