Crawlora MCP

modrinth_files_update_individual

Read-only

Resolve compatible updates for several Modrinth files with independent per-file loader and game-version filters in one native POST read, returning a map of update records from each requested hash to its matching version object. Each entry in the hashes array carries its own hash and optional filters; use modrinth_files_update when every file shares one filter set.

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

Input Schema

Name	Required	Description	Default
`hashes`	Yes	Required JSON array of per-file lookups, each with its own hash and optional loader/game-version filters. An empty array is valid.
`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.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 real context beyond that: it is a single native POST read (one network call for a batch) and returns a hash-to-version map, which matters for batching decisions. It stops short of mentioning rate limits, error behavior for unresolvable hashes, or partial-failure semantics.

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?

Two sentences, no filler, with scope and return shape front-loaded before the alternative-tool routing. The first sentence is dense and slightly overloaded, but every clause carries information.

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

Completeness4/5

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

With an output schema, full schema coverage, and safety annotations, the description only needs to convey purpose, batching behavior, and sibling routing, all of which it does. Minor gaps (partial failure handling for individual hashes, pagination or size limits on the batch) are the only things an agent might still wonder about.

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 hash format, loader/game-version discovery paths, empty-array semantics, and algorithm auto-detection are already documented. The description reinforces the key semantic (each entry carries its own filters) but adds no format or syntax detail beyond the schema, so baseline 3 applies.

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 compatible updates for several Modrinth files) plus the defining scope: independent per-file loader and game-version filters in a single request. It also names the return shape (map of hash to matching version), which lets an agent distinguish it from the sibling update tools.

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?

Explicitly routes the agent: use modrinth_files_update when every file shares one filter set, implying this tool is for heterogeneous filters. That is a concrete when-to-use/when-to-use-the-alternative split, not mere implication.

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.