Skip to main content
Glama

List every Minecraft version + namespace linkie carries

mc_list_versions

Check which Minecraft versions exist for each mappings namespace (e.g., Yarn, Mojang). Filter by namespace, version prefix, and optionally include unstable releases like snapshots.

Instructions

Live call to https://linkieapi.shedaniel.me/api/namespaces. Returns every mappings namespace (yarn, mojang, mojang_raw, quilt-mappings, mcp, legacy-yarn, feather, ...) and which Minecraft versions each one currently has. Use to confirm a version exists before searching it. By default filters to stable releases — pass includeUnstable=true to see snapshots, pre-releases, RCs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
namespaceNoFilter to one namespace. Omit to list all.
versionPrefixNoFilter to versions starting with this string (e.g. '1.21' or '26.1').
includeUnstableNoInclude snapshots/pre/rc. Default false.
limitNoMax versions per namespace. Default 30.

Implementation Reference

  • The mc_list_versions tool handler. It calls listNamespaces() from linkie.ts, applies optional filters (namespace, versionPrefix, includeUnstable, limit), and formats the output.
      "mc_list_versions",
      {
        title: "List every Minecraft version + namespace linkie carries",
        description:
          "Live call to https://linkieapi.shedaniel.me/api/namespaces. Returns " +
          "every mappings namespace (yarn, mojang, mojang_raw, quilt-mappings, " +
          "mcp, legacy-yarn, feather, ...) and which Minecraft versions each one " +
          "currently has. Use to confirm a version exists before searching it. " +
          "By default filters to stable releases — pass includeUnstable=true to " +
          "see snapshots, pre-releases, RCs.",
        inputSchema: {
          namespace: LinkieNamespaceSchema.optional().describe(
            "Filter to one namespace. Omit to list all.",
          ),
          versionPrefix: z
            .string()
            .optional()
            .describe("Filter to versions starting with this string (e.g. '1.21' or '26.1')."),
          includeUnstable: z.boolean().optional().describe("Include snapshots/pre/rc. Default false."),
          limit: z.number().int().positive().max(500).optional().describe("Max versions per namespace. Default 30."),
        },
      },
      async ({ namespace, versionPrefix, includeUnstable, limit }) => {
        const cap = limit ?? 30;
        let namespaces;
        try {
          namespaces = await listNamespaces();
        } catch (err) {
          return text(`Failed to reach linkie: ${(err as Error).message}`);
        }
        const filtered = namespace ? namespaces.filter((n) => n.id === namespace) : namespaces;
        const lines: string[] = [];
        for (const ns of filtered) {
          const versions = ns.versions
            .filter((v) => includeUnstable || v.stable)
            .filter((v) => !versionPrefix || v.version.startsWith(versionPrefix))
            .slice(0, cap)
            .map((v) => (v.stable ? v.version : `${v.version} _(unstable)_`));
          if (versions.length === 0) continue;
          lines.push(`## ${ns.id} (${versions.length}${versions.length === cap ? "+" : ""} versions)`);
          lines.push(versions.map((v) => `- ${v}`).join("\n"));
          lines.push("");
        }
        if (lines.length === 0) {
          return text(
            `No matches. Try without filters, or check namespace name. ` +
              `Available namespaces: ${namespaces.map((n) => n.id).join(", ")}.`,
          );
        }
        return text(lines.join("\n").trim());
      },
    );
  • Input schema definition for mc_list_versions: optional namespace, versionPrefix, includeUnstable, and limit fields.
    server.registerTool(
      "mc_list_versions",
      {
        title: "List every Minecraft version + namespace linkie carries",
        description:
          "Live call to https://linkieapi.shedaniel.me/api/namespaces. Returns " +
          "every mappings namespace (yarn, mojang, mojang_raw, quilt-mappings, " +
          "mcp, legacy-yarn, feather, ...) and which Minecraft versions each one " +
          "currently has. Use to confirm a version exists before searching it. " +
          "By default filters to stable releases — pass includeUnstable=true to " +
          "see snapshots, pre-releases, RCs.",
        inputSchema: {
          namespace: LinkieNamespaceSchema.optional().describe(
            "Filter to one namespace. Omit to list all.",
          ),
          versionPrefix: z
            .string()
            .optional()
            .describe("Filter to versions starting with this string (e.g. '1.21' or '26.1')."),
          includeUnstable: z.boolean().optional().describe("Include snapshots/pre/rc. Default false."),
          limit: z.number().int().positive().max(500).optional().describe("Max versions per namespace. Default 30."),
        },
      },
  • src/index.ts:627-628 (registration)
    Tool registration via server.registerTool('mc_list_versions', ...) at line 627-628.
    server.registerTool(
      "mc_list_versions",
  • The listNamespaces() helper function that fetches namespace+version data from linkie's API, with caching.
    export async function listNamespaces(): Promise<LinkieNamespace[]> {
      return cached("linkie", "namespaces", 60 * 60 * 1000, async () => {
        const res = await fetch(`${LINKIE_API_BASE}/api/namespaces`);
        if (!res.ok) throw new Error(`linkie /api/namespaces: HTTP ${res.status}`);
        return (await res.json()) as LinkieNamespace[];
      });
    }
  • The LinkieNamespace interface used by mc_list_versions to represent namespace/version data.
    export interface LinkieNamespace {
      id: string;
      versions: { version: string; stable: boolean }[];
    }
Behavior4/5

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

With no annotations, the description must disclose all behavioral traits. It discloses it's a live API call, the default stable filter, and the parameter to include unstable versions. It does not mention rate limits, authentication, or side effects, but for a read-only list operation this is adequate.

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 two sentences, front-loaded with the main purpose. Every sentence provides essential information without redundancy or fluff.

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?

Given 4 parameters, no output schema, and no annotations, the description covers the tool's purpose, default behavior, and key parameter usage. It doesn't detail the return format, but the core use case is well-addressed.

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?

Schema coverage is 100%, and the description adds value by explaining the default behavior of includeUnstable ('By default filters to stable releases') and clarifying that omitting namespace lists all. This goes beyond the schema descriptions, which state defaults but not implications.

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 clearly states the tool lists all Minecraft versions per namespace from the Linkie API. It distinguishes itself from sibling tools like mc_version_info by focusing on namespaces and version availability, with a specific verb ('lists') and resource ('namespaces/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 description explicitly says 'Use to confirm a version exists before searching it,' providing clear usage context. It also explains the default filtering (stable releases) and how to include unstable versions. However, it does not explicitly state when not to use this tool or mention alternatives among siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ratph6/mc-mod-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server