Skip to main content
Glama
Sign In
mcgl-mcp

mcgl-mcp

by exi66
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Single post

forum_get_post
Read-only

Retrieve a single Minecraft Galaxy forum post by ID, including its position in the topic and the topic/page context it belongs to.

Instructions

One post by id (e.g. from a /post/2120899 link) with its number in the topic, plus the topic and the forum_get_topic page (default pageSize) it is on. Same post format as forum_get_topic.

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": "forum_get_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
postIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0-dev

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real value beyond them by disclosing the return envelope — the post, its ordinal in the topic, its parent topic, and the page location — plus a cross-reference establishing format parity with forum_get_topic.

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?

Two sentences, front-loaded with the identity of the resource and followed by the disclosure of extra context. The middle clause ('plus the topic and the forum_get_topic page (default pageSize) it is on') is a bit dense but every element carries information.

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 one parameter, no output schema, and safe-read annotations, this description covers the essentials: what comes back, how the id is sourced, and how the payload relates to the sibling tool. Nothing an agent needs in order to call it correctly is missing.

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 0%, so the description must carry the load, and it does: the sole parameter is explained as a post id obtainable from a URL path like /post/2120899. The parenthetical '(default pageSize)' hints at how page context is computed, though it is slightly ambiguous since no pageSize parameter exists in the schema.

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 names a specific resource and scope ('One post by id') and goes further by stating the extra context returned: the post's number in the topic, the topic, and the page it sits on. 'Same post format as forum_get_topic' explicitly distinguishes it from the sibling that returns whole topics, so an agent can choose without opening either schema.

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?

It gives an input-provenance cue ('e.g. from a /post/2120899 link'), which implies when the tool is applicable, but there is no explicit when-to-use/when-not guidance or named alternative for related lookups. Usage is implied rather than stated.

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