Skip to main content
Glama
Sign In
Minecraft Wiki MCP

Minecraft Wiki MCP

by L3-N0X
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

MinecraftWiki_getSectionsInPage

Retrieve all section headings from a Minecraft Wiki page to navigate content and locate specific information efficiently.

Instructions

Retrieves an overview of all sections in the page.

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": {
      "title": "<title>"
    },
    "name": "MinecraftWiki_getSectionsInPage"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesTitle of the page to retrieve sections for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It states it 'retrieves an overview' but doesn't clarify what 'overview' entails (e.g., section titles, IDs, hierarchy), whether it's read-only, if there are rate limits, or authentication needs. This leaves key operational traits undisclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence with zero wasted words. It's front-loaded with the core action and resource, making it efficient and easy to parse without unnecessary elaboration.

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

Completeness2/5

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

Given no annotations and no output schema, the description is incomplete for a tool that likely returns structured section data. It doesn't explain the return format (e.g., list of sections with metadata), leaving the agent guessing about output behavior despite the simple input schema.

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 description coverage is 100%, with the single parameter 'title' well-documented in the schema. The description adds no additional parameter semantics beyond implying it's for a page, which the schema already covers. This meets the baseline for high schema coverage but doesn't enhance understanding.

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 clearly states the action ('Retrieves an overview') and resource ('all sections in the page'), making the purpose understandable. However, it doesn't explicitly differentiate from siblings like 'MinecraftWiki_getPageSection' (which gets specific section content) or 'MinecraftWiki_getPageContent' (which gets full page content), missing the opportunity for perfect sibling distinction.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention siblings like 'MinecraftWiki_getPageSection' for detailed content or 'MinecraftWiki_getPageContent' for full text, leaving the agent to infer usage from tool names alone without explicit context.

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