Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

modrinth_file_version

Resolve a Modrinth project version from a file hash and return its native public metadata; specify SHA-1 or SHA-512, or let auto-detection handle the algorithm.

Instructions

Resolve a version by file hash. 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": {
      "hash": "<hash>"
    },
    "name": "modrinth_file_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
hashYesNative hash
algorithmNoFile-hash algorithm; omitted uses native auto-detection

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden. It does disclose that results are public Modrinth metadata, but it says nothing about what happens when a hash is unknown, whether the call is read-only, or about rate limits, deferring all of that to an external 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?

It is short and front-loads the core action, but the final sentence is a pointer to external documentation rather than information, so one of three sentences does not earn its place.

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

Completeness3/5

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

There is no output schema and no annotations, so the description should convey more about the returned metadata and failure modes. "Native public Modrinth metadata" is directionally useful but too abstract for an agent to anticipate the response, and the external reference is not a substitute within the definition.

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%, including an enum for algorithm and a note that omission triggers native auto-detection, so the schema already does this work. The description adds only the notion of hashing being the lookup key, which is the baseline for fully documented parameters.

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?

"Resolve a version by file hash" gives a specific verb and lookup key, so the agent knows exactly what the tool acts on. It does not, however, contrast itself with near-neighbours such as modrinth_file_versions or modrinth_project_version, leaving the boundary to be inferred.

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 statement of when to prefer this hash-based lookup over the sibling version tools, and no prerequisites or exclusions. The only routing hint is "see the endpoint reference", which pushes guidance outside the definition entirely.

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