Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

modrinth_file_versions

Resolve Modrinth file hashes to their corresponding versions and return native public metadata for each resource.

Instructions

Resolve file hashes to versions. 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_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesNative metadata lookup body

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

C2.8/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. Saying it returns 'native public Modrinth metadata' implies no auth is needed, but nothing is said about rate limits, error behavior for unknown hashes, or response shape. The instruction to 'see the endpoint reference' points at documentation the calling agent does not have, so it does not compensate.

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 leading sentence is well front-loaded and earns its place. The remaining two sentences are largely filler: 'native public Modrinth metadata' is vague, and the pointer to an external endpoint reference is not actionable for the agent.

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?

There is no output schema, so the description must explain what comes back, and it does not: 'native public Modrinth metadata' and 'see the endpoint reference' defer the essential information. For a tool with a nested request body and no annotations, this leaves the agent without enough to call it confidently.

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 nested body, hashes array, and sha1/sha512 algorithm enum are already documented structurally. The description adds no detail beyond that, such as a default algorithm or accepted hash formats, so the baseline of 3 applies.

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 first sentence states a specific verb and resource: resolve file hashes to versions. That is far more informative than the name alone and lets an agent separate it from sibling lookups like modrinth_file_projects or modrinth_versions. It stops short of explicitly contrasting itself with the singular modrinth_file_version, so it is clear but not sibling-differentiated.

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 statement of when to use this tool versus alternatives such as modrinth_file_version or modrinth_project_versions, and no prerequisites or exclusions. The hash-based lookup is implied by the purpose sentence, but the agent is left to infer the selection criteria from the name.

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