Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

modrinth_files_update_individual

Resolve Modrinth file updates with per-file hash filters and optional loader or game-version constraints, returning native public metadata for each requested resource.

Instructions

Resolve updates with per-file filters. 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_individual"
  }
}

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?

No annotations are provided, so the description carries the full behavioral burden. It discloses that native public Modrinth metadata is returned, but does not explain whether 'resolve updates' is a read-only lookup or a mutation, what permissions are needed, or how results are matched to hashes.

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 definition is short and front-loaded, but the opening sentence is ambiguous and the final sentence defers to an external endpoint reference that may not be available to the agent. It is concise, but not every sentence contributes actionable information.

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 body object and no output schema or annotations, so the description should explain more about matching behavior and return values. Instead it gives only a high-level statement and an external reference, leaving important context absent.

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 body structure, required hash objects, optional loaders/game_versions, and algorithm enum. The description adds no parameter-specific meaning beyond the schema, which is the baseline for high coverage.

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 gives a vague verb phrase, 'Resolve updates with per-file filters,' and says it returns Modrinth metadata, so the general area is inferable. It does not clearly differentiate this tool from siblings such as modrinth_files_update or modrinth_files_update_many, and 'this resource' is imprecise.

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?

The phrase 'per-file filters' hints at a use case but gives no explicit when-to-use guidance. It does not say when to choose this individual variant over the bulk update siblings or what prerequisites apply.

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