Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

modrinth_project_version

Fetch a Modrinth project version by ID or version number and return its native public metadata for release, dependency, or compatibility checks.

Instructions

Get a project version by number or ID. Returns the native public Modrinth metadata for this resource. See the endpoint reference for exact request and response behavior.

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

NameRequiredDescriptionDefault
idYesNative id
numberYesNative number

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It says the tool returns "native public Modrinth metadata" and is implicitly a read, but it discloses nothing about error behavior for unknown IDs, whether both identifiers must match the same version, or response shape; instead it defers to an external "endpoint reference."

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

Conciseness3/5

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

The first sentence is front-loaded and efficient, but the third sentence, "See the endpoint reference for exact request and response behavior," is boilerplate that offloads meaning rather than conveying it.

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

Completeness2/5

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

For a tool with no annotations and no output schema, the description should explain return content and identifier semantics. It instead points outside the definition, leaving the required-both-identifiers question and the lookup's failure mode undocumented.

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 two parameters are documented in structured form and the baseline is 3. The description's phrase "by number or ID" suggests either identifier suffices, while the schema marks both id and number as required, a mismatch the description does not resolve.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource: "Get a project version by number or ID." That is enough for an agent to know it retrieves a single version record, though it does not distinguish this from siblings such as modrinth_version, modrinth_project_versions, or modrinth_file_version.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus the closely named siblings, nor any preconditions or exclusions. The agent is left to infer from the name alone whether this fetches one version, many versions, or a file-level version.

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

Deploy Server

Other Tools