Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

modrinth_version

Read-only

Get one Modrinth version by its own version id and return its native metadata: id, project_id, name, version_number, channel, date_published, loaders, game_versions, featured flag, downloads and every file with filename, primary flag, size, hashes and CDN URL. Get version ids from modrinth_project_versions or modrinth_versions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
idYesRequired Modrinth version id, for example aFVpk3tG.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that this is a direct single-record native-metadata read with no transformation, but says nothing about failure behavior for an unknown or malformed id, rate limits, or caching — modest added value beyond the structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action and scope, followed by the routing hint. The long enumeration of return fields is largely redundant with the existing output schema, which costs some economy, but nothing is ambiguous or padded with filler.

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 one-parameter read with an output schema and read-only annotations, this is essentially complete: purpose, input source, and payload shape are all covered. The only gap is error/edge-case behavior for invalid ids, which is minor given the low complexity.

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 coverage is 100% and the schema already defines the id with an example. The description adds only the clarification that this is the version's own id (not a project id) and where to obtain it; helpful but marginal against a fully documented single parameter, so baseline 3 applies.

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?

States a specific verb and resource ('Get one Modrinth version by its own version id') and explicitly distinguishes it from the list-style siblings by emphasizing 'one' and 'its own version id'. The returned metadata is enumerated, so an agent knows exactly what this returns versus the version-list 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?

Gives concrete routing guidance for the prerequisite: 'Get version ids from modrinth_project_versions or modrinth_versions.' It does not state when NOT to use this tool (e.g. use modrinth_file_version to look up by file hash or modrinth_project_version for a project's latest), so it falls short of full alternative coverage.

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

All Crawlora MCP 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