Crawlora MCP

modrinth_project_version

Read-only

Get one version of one Modrinth project by the project's id or slug plus a version number or version id, returning the same native version object as modrinth_version. Use this when you already know the project, and get the number from modrinth_project_versions; an unknown number returns 404.

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>",
      "number": "<number>"
    },
    "name": "modrinth_project_version"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Required Modrinth project id or slug.
`number`	Yes	Required version number or version id within the project, for example mc26.3-0.9.3-beta.3-fabric or aFVpk3tG.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 11, 2026

TDQS

A4.3/5.0

Behavior4/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 useful behavioral detail beyond annotations: the return object matches modrinth_version, and an unknown version number produces a 404. It does not discuss authentication or rate limits, but those are not critical here given the annotations and output schema.

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?

Two tightly written sentences with no wasted wording. The primary purpose is front-loaded, followed immediately by usage guidance and error behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has an output schema and full parameter schema coverage, so the description does not need to explain return fields. It still provides enough context about identity, sourcing the version number, output equivalence, and the 404 case for an agent to invoke it correctly.

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%, so the input schema already explains both parameters thoroughly, including examples. The description restates that the project parameter accepts an id or slug and the version parameter accepts a number or id, adding little beyond the schema other than where to source the version number.

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 version of one Modrinth project, using a project identifier plus a version identifier. It also distinguishes itself from modrinth_version by saying it returns the same native version object, and from modrinth_project_versions by directing users there to obtain the version number.

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?

Explicitly says to use this when the project is already known and to get the version number from modrinth_project_versions. It also explains the unknown-number outcome as a 404. It does not explicitly state when to prefer modrinth_version instead, though the output-equivalence note implies the relationship.

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

All Crawlora MCP tools Inspect

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.