Crawlora MCP

modrinth_file_projects

Read-only

Resolve a batch of file hashes to the Modrinth projects that contain them in one native POST read and return a map from each requested hash to its project object (id, slug, title, project type and counters). 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.

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_projects"
  }
}

Input Schema

Name	Required	Description	Default
`hashes`	Yes	Required 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.
`algorithm`	No	Optional hash algorithm, sha1 or sha512; omit it for native auto-detection from the first hash.

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/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), yet the description adds genuinely new behavior: unknown hashes are silently omitted rather than erroring, and an empty array is a valid no-error input. It also discloses the response shape (map from hash to project object with id, slug, title, type, counters). What is missing is any batch-size limit or rate-limit context, which matters for a bulk endpoint.

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 core action and result, and the second sentence carries only input-format and edge-case facts. The first sentence is dense with a parenthetical field list, but every clause is informative rather than filler.

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, full schema coverage and an output schema, the description only needs to supply edge-case and mechanism facts, and it does: valid empty input, silent omission of unknown hashes, auto-detection of algorithm, and single-request semantics. An agent can call this correctly without further context.

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 parameters are already documented by the schema. The description restates the hash format (40-char SHA-1 / 128-char SHA-512) and the auto-detection behavior of 'algorithm', which is useful reinforcement but adds no meaning beyond the schema's own text.

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 the Modrinth projects that contain them') plus the mechanism ('one native POST read'). The batch-resolution scope distinguishes it clearly from single-resource siblings such as modrinth_file_version and from the search tools.

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

Usage Guidelines3/5

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

The phrase 'in one native POST read' strongly implies this is the bulk path versus per-hash lookups, but the description never names an alternative or states explicit when-to-use / when-not-to-use conditions. Usage is inferable rather than specified.

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.