Retrieve available Minecraft or mod loader versions from Prism's meta API by kind or loader alias, with an optional limit, to choose compatible versions for instances.
List versions from Prism's meta API. kind: 'minecraft' or a loader alias (forge/fabric/neoforge/quilt/liteloader) or a full meta uid.
| Name | Required | Description | Default |
|---|---|---|---|
| kind | Yes | ||
| limit | No |
Changes observed during successful MCP inspections.
v0.9.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It does not say whether this hits a remote service, whether results are cached, how pagination via 'limit' behaves, or what the response looks like — all material for a network-backed list call.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, front-loaded with the purpose, and the parameter detail follows immediately. Nothing is wasted or repeated.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema and no annotations means the description must stand alone, and it does for purpose and 'kind'. Gaps remain on 'limit' semantics, result shape, and whether this is a remote call, which matters for an external meta-API tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%, and the description compensates well for 'kind' by enumerating 'minecraft', loader aliases, and full meta uids — far beyond the bare 'string' type. However, 'limit' is never mentioned, so half the parameters remain undocumented.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('List versions') and names the source ('Prism's meta API'). It's distinguishable from siblings like list_mod_versions or list_mod_files_cf by the meta-API framing, though it never explicitly contrasts with them.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The 'kind' explanation implies the use case (fetching Minecraft or loader versions), but there is no explicit when-to-use, when-not-to-use, or named alternative. The agent must infer that this is for game/loader versions rather than mod versions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.