Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

modrinth_file_versions

Read-only

Resolve a batch of file hashes to their Modrinth versions in one native POST read and return a map from each requested hash to its version object (id, project_id, version number, loaders, game versions and file hashes). Send a JSON array of SHA-1 (40 hexadecimal characters) or SHA-512 (128 hexadecimal characters) hashes; an empty array is valid and unknown hashes are omitted. Use modrinth_file_version for a single hash.

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": {
      "hashes": "<hashes>"
    },
    "name": "modrinth_file_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
hashesYesRequired JSON array of file hashes to resolve (40 hexadecimal SHA-1 or 128 hexadecimal SHA-512 characters). An empty array is valid and returns an empty map.
algorithmNoOptional hash algorithm, sha1 or sha512; omit it for native auto-detection from the first hash.

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

A4.5/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 description focuses on behavior the annotations can't express: the single POST round-trip, the hash-to-version map return, and that unknown hashes are silently dropped rather than erroring. It does not mention rate limits or failure modes for malformed hashes, which keeps it below a 5.

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?

Three sentences, front-loaded with purpose then input contract then sibling routing. Nothing is wasted; the repetition of hash lengths mirrors the schema but is the only mild redundancy.

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?

With annotations covering the safety profile, a 100%-covered input schema, and an output schema handling return values, the description supplies everything else an agent needs: batching semantics, empty-array validity, and unknown-hash handling.

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%, so both hashes and algorithm are already documented in the schema, including hex lengths and the auto-detection default. The description restates the hash format but adds no new semantics beyond what the schema provides, making the baseline 3 correct.

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 ("Resolve a batch of file hashes to their Modrinth versions"), the batch scope, the transport ("one native POST read"), and the return shape. It explicitly distinguishes itself from modrinth_file_version, so an agent can pick it without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit routing rule: batch hashes go here, a single hash goes to modrinth_file_version. It also states the expected input format and edge-case behavior (empty array valid, unknown hashes omitted), which tells the agent both when to use it and what to expect.

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