Skip to main content
Glama

MCJars

by com.mcjars
OverviewDiscussionsAdmin

Resolve a server download

get_download
Read-onlyIdempotent

Get an exact provider build or the newest matching build when version is omitted. Minecraft and loader versions are separate: use minecraftVersion for the game, version for the full provider build. Returns URLs only; does not download or execute files. No match returns an error without substituting another game version or channel.

Input Schema

NameRequiredDescriptionDefault
osNoRequested platform. Linux and Windows also accept universal downloads.
channelNostable
contextYesExplain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
versionNoExact full provider build from list_versions. Omit to select the newest matching build.
providerYesProvider slug from list_providers, such as paper or fabric.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
conversation_idNoPass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.
minecraftVersionNoExact Minecraft game version, such as 1.21.1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations, the description discloses important behavior: it returns URLs only and does not download or execute files. It also states that no match produces an error without substituting another game version or channel, which is useful failure-mode context.

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 short, front-loaded with the core operation, and each sentence adds distinct value. The separation rule, return-only behavior, and no-match behavior are all stated without repetition.

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 the high schema coverage and absence of an output schema, the description provides the key behavioral context an agent needs: version semantics, URL-only return behavior, and error behavior. It could still be slightly more explicit about using list_providers/list_versions first, but the schema covers that adequately.

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 already high at 88%, so most parameter meaning is documented in the schema. The description still adds value by explicitly separating minecraftVersion for the game from version for the full provider build and by reinforcing the omitted-version behavior.

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 uses a specific verb/resource combination ('Get an exact provider build or the newest matching build') and immediately clarifies the scope when version is omitted. It also distinguishes its output from a download action by stating it returns URLs only, which helps separate it from sibling listing tools.

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?

It clearly explains the selection behavior when version is omitted and how minecraftVersion differs from version. It does not explicitly name list_providers or list_versions as prerequisites, though the schema parameter descriptions do reference them.

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

All MCJars toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources