Skip to main content
Glama

mc_read_reference

Reads a specific API reference file inside a Minecraft modding skill, so you can pull exact Forge, Fabric, or Paper API details after listing available files with mc_read_skill.

Instructions

Read an API reference file within a skill. Use mc_read_skill first to see available reference files.

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": {
      "path": "<path>"
    },
    "name": "mc_read_reference"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesRelative path under skills/, e.g. minecraft-forge-mod/references/api/forge-1.12.2-api.md

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. "Read" implies a non-mutating fetch and the discovery-before-read workflow is disclosed, but nothing is said about failure behavior for a bad/relative path, file size or truncation, or what the returned content looks like.

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?

Two short sentences, zero filler, with the action front-loaded and the prerequisite immediately following. Every clause earns its place.

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?

For a one-parameter read tool with no output schema and no annotations, the definition covers purpose and workflow ordering adequately. The remaining gap is minor: no hint about what content is returned or how a missing path surfaces.

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% and the single path parameter is documented in-schema with an example relative path under skills/. The description adds essentially nothing beyond "within a skill", so the baseline 3 applies.

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?

Specific verb+resource: "Read an API reference file within a skill" tells the agent exactly what is fetched, and it is clearly distinct from mc_read_skill, which lists the references rather than reading one. It stops short of naming an explicit alternative path, but the verb/resource pair 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?

The second sentence supplies a concrete prerequisite and ordering: call mc_read_skill first to discover which reference files exist. That is real when-to-use guidance; what is missing is any statement of when not to use this tool (e.g. when the target is a SKILL.md rather than a reference file).

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