Skip to main content
Glama

mc_read_skill

Reads a named Minecraft development skill document and returns its full content, giving guidance for building Paper, Fabric, Forge, NeoForge, or Spigot projects correctly.

Instructions

Read a Minecraft development skill document. Returns the full skill content for the specified skill name.

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": {
      "skill": "<skill>"
    },
    "name": "mc_read_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
skillYesSkill name to read

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden; it does signal a read-only retrieval and says exactly what comes back (full content, not a summary). It says nothing about content size, behavior on an invalid skill name, or whether the document is cached, which matters for a no-annotation tool.

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 short sentences, front-loaded with the action, and nothing extraneous. The second sentence largely restates what "read a skill document" already implies, so it is close to but not perfectly economical.

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

Completeness3/5

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

For a simple one-parameter read tool with a complete enum and no output schema, the description is adequate: it says what is returned. It remains incomplete on how this differs from the sibling reference reader and on any practical limits of the returned document.

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?

Only one parameter and it is 100% covered by the schema, including a fully enumerated value set, so the baseline is 3. The description's "for the specified skill name" adds no meaning beyond the schema's own "Skill name to read" description and enum.

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 uses a specific verb+resource pair ("Read a Minecraft development skill document") and states the return value (full skill content). It is clear on its own but never distinguishes itself from the closest sibling, mc_read_reference, which an agent could easily confuse with it.

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?

No when-to-use guidance is given, no prerequisites, and no exclusions. The phrase "Returns the full skill content" hints at full-fetch vs. lookup usage but stops short of saying when to reach for this versus mc_read_reference or mc_scaffold.

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