MC Source MCP Server

List Versions

list_versions

List Minecraft versions filtered by type (release, snapshot, or unobfuscated) with an optional limit. Get available versions for your modding or decompilation tasks.

Instructions

List available Minecraft versions

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

Input Schema

Name	Required	Description	Default
`type`	No	Filter by version type (release, snapshot, or unobfuscated)
`limit`	No	Limit the number of versions returned

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 9, 2026

TDQS

A3.8/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'List available Minecraft versions', which essentially restates the tool's name. It does not mention any filtering behavior, ordering, default limits, or what data is returned, leaving the agent without key operational details.

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, concise sentence that directly communicates the tool's purpose. Every word earns its place, and there is no redundancy or unnecessary detail.

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 list tool, the description is adequate. The schema covers all parameters, and the absence of an output schema is compensated by the obvious nature of 'List versions' (returns a list of versions). However, there's no mention of return format or ordering, so it falls short of a perfect score.

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% for both parameters (type and limit) and includes a default value for limit. The description itself adds no parameter-specific information, so it does not enhance the schema. Baseline 3 is appropriate because the schema fully documents the parameters.

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 'List available Minecraft versions' clearly states the verb (List) and resource (Minecraft versions). It is unambiguous and distinct from sibling tools like search_classes and decompile_class, which deal with classes rather than versions.

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 intended use is clear from the description alone: it lists versions. While it doesn't explicitly mention when to use this over alternatives, the sibling tools are evidently unrelated, so the context is sufficient. No exclusions or alternate recommendations are given, but none seem necessary.

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

Deploy Server