Skip to main content
Glama

mc_list_versions

Lists all supported platform and Minecraft version combinations with their default Java levels, helping you pick the right target before scaffolding a mod or plugin project.

Instructions

List all supported platform × Minecraft version combinations with default Java levels.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mc_list_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. 'List' strongly implies a read-only enumeration, and the description discloses the returned content (platform × version combinations with default Java levels). It does not explicitly confirm safety, auth requirements, pagination, or output format, leaving some behavioral gaps.

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 definition is a single, front-loaded sentence with no filler. Every phrase – 'List all', 'supported platform × Minecraft version combinations', and 'with default Java levels' – adds specific meaning.

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 simple zero-parameter list tool with no output schema, the description gives enough context to understand what is returned: supported platform/version combinations and their default Java levels. It could be slightly more complete by hinting at the output shape, but the core information is present.

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?

The tool has zero parameters, and the input schema is empty with 100% coverage. There are no parameter semantics to clarify, so the baseline of 4 is appropriate.

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 clear verb, 'List', and a precise resource: 'supported platform × Minecraft version combinations with default Java levels.' It is easily distinguishable from sibling tools like mc_gradle, mc_read_reference, mc_read_skill, and mc_scaffold, though it does not explicitly contrast itself with any of them.

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?

Usage is implied by 'List all supported ... combinations' – an agent can infer this is for enumerating supported platform/version pairs and their default Java levels. However, there is no explicit when-to-use guidance, no exclusions, and no named alternatives, so the agent must infer context.

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