Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

modrinth_file_projects

Resolve file hashes to their Modrinth projects and return native public metadata for matching resources.

Instructions

Resolve file hashes to projects. 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_file_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesNative metadata lookup body

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it does little: it implies a read-only lookup but never states that explicitly, and says nothing about rate limits, batch size limits for the hashes array, or what the response contains for hashes that match no project. Deferring to an external endpoint reference provides no in-band context.

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 short sentences with the core purpose front-loaded and no redundant wording. The closing "See the endpoint reference" line is low-value filler that does not earn its place, which keeps it below a 5.

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

Completeness3/5

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

The tool is simple (one nested body parameter, no output schema), so the schema does most of the work, but the description leaves meaningful gaps: unmatched-hash behavior and the algorithm selection are unaddressed. For a lookup whose entire value is the hash-to-project mapping, that is adequate but not complete.

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% and each field carries its own description, so the schema already documents the body, hashes array, and algorithm enum. The description adds no meaning beyond that — notably it never clarifies the significant sha1 vs sha512 choice or whether the algorithm may be omitted — so the baseline of 3 is appropriate.

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?

"Resolve file hashes to projects" gives a specific verb (resolve) and resource mapping (hash → project), which is more precise than the sibling names alone convey. It stops short of distinguishing itself from adjacent file/version lookup siblings, so an agent must still infer which lookup fits a given input.

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 description implies the use case (you have file hashes and want the owning project), but there is no explicit when-to-use versus alternatives such as the file-version lookup tools, and no mention of prerequisites or call ordering. "See the endpoint reference" pushes guidance out of the definition rather than into 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