Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

modrinth_file_update

Read-only

Resolve the latest compatible update for one Modrinth file and return the version object that satisfies the requested loader and game-version filters. Pass the file's hash, optionally its algorithm, and optional loaders and game_versions arrays validated against modrinth_tags; omitted filters keep the site's native behaviour. This is a read-only lookup, never an installation or write.

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

Input Schema

NameRequiredDescriptionDefault
hashYesRequired file hash of the file whose compatible update is resolved: 40 hexadecimal SHA-1 or 128 hexadecimal SHA-512 characters.
loadersNoOptional loader names to filter compatible updates. Discover the values with modrinth_tags and type=loader. An explicit empty array stays distinct from omission.
algorithmNoOptional hash algorithm, sha1 or sha512; omit it for native auto-detection.
game_versionsNoOptional game versions to filter compatible updates. Discover the values with modrinth_tags and type=game_version. An explicit empty array stays distinct from omission.

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

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is largely pre-covered. The description adds that omitted filters preserve the site's native behaviour and that this is 'never an installation or write' – valuable given the misleading 'update' name – but it doesn't touch rate limits, empty-result behaviour, or how the version object is chosen among candidates. Contradiction check: 'read-only lookup' agrees with readOnlyHint=true, so there is no annotation contradiction.

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?

Three sentences, front-loaded with the operation and return type, then the parameters, then the safety clarification. The closing 'never an installation or write' slightly restates the readOnlyHint annotation, but is defensible padding given the tool's misleading name.

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 only four parameters, full schema coverage and an output schema, the description covers what an agent needs: purpose, filter semantics, discovery path via modrinth_tags, and the read-only nature. Only the choice between this and the batch update siblings remains unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description still adds meaning by flagging that loader and game_version values must be validated against modrinth_tags and that omission differs from an explicit empty array. It does not restate hash format or algorithm values, which the schema already covers.

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 opens with a specific verb and resource ('Resolve the latest compatible update for one Modrinth file') and states the return value ('the version object'). The phrase 'one Modrinth file' implicitly distinguishes it from the plural batch siblings (modrinth_files_update, modrinth_files_update_many), but no sibling is named explicitly, keeping it short of a 5.

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

Usage Guidelines4/5

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

It gives clear context for use: supply a single file hash plus optional loader/game-version filters, and points to modrinth_tags (type=loader / type=game_version) for discovering valid filter values. It never states when to prefer the batch or single-version siblings instead, so no explicit exclusions.

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