Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

modrinth_files_update_many

Find compatible update versions for multiple files by submitting hashes, loaders, and game versions; returns native Modrinth metadata.

Instructions

List compatible update versions for files. 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": {
      "body": "<body>"
    },
    "name": "modrinth_files_update_many"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesNative metadata lookup body

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

C2.5/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It states that it returns native public Modrinth metadata, which is useful, but does not clarify whether any files are modified, whether this is read-only, what permissions are required, or what the response looks like.

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?

The first sentence is front-loaded and reasonably concise, but the second and third sentences add little beyond boilerplate and a deferral to an external endpoint reference. The definition is short, yet part of its length does not earn its place.

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

Completeness2/5

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

The tool has a nested request body, no output schema, and no annotations, so the description needs to be relatively complete. Instead, it defers exact request and response behavior to an external reference and never resolves the apparent read-versus-update ambiguity.

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 schema already documents the nested body fields. The description adds only a light hint that hashes refer to files and that loaders/game_versions relate to compatibility filtering; it does not add syntax or selection semantics beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ('List compatible update versions for files'), but the tool name 'update_many' implies a bulk mutation while the description describes a read-like lookup. That conflict leaves the agent unsure whether this tool updates files or merely lists versions. It also does not distinguish this tool from siblings such as modrinth_files_update_individual.

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 explicit guidance on when to use this tool versus the sibling update tools or when not to use it. The only direction is 'See the endpoint reference,' which defers usage guidance outside the definition rather than providing it.

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