Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

modrinth_versions

Fetches native Modrinth metadata for multiple version IDs from a JSON-encoded array, returning structured public data for each resource.

Instructions

Get native multiple-version metadata. 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": {
      "ids": "<ids>"
    },
    "name": "modrinth_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesJSON-encoded array of native identifiers; absent members are omitted

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

C2.3/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 burden. It says the call returns public Modrinth metadata, but is silent on auth requirements, rate limits, error behavior for unknown IDs, and the shape or size of the response; the one behavioral clause ("absent members are omitted") lives in the schema, not the description.

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?

It is short and front-loaded, but the second sentence largely restates the first and the third is a non-actionable pointer to a document the agent does not have. Two of three sentences do not earn their 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?

For a simple single-parameter lookup this could be adequate, but with no annotations and no output schema the description should at least characterize the returned metadata and identifier format. Instead it outsources that to an unavailable endpoint reference, leaving real gaps.

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 the single ids parameter is already documented as a JSON-encoded array with omitted members, so the schema does the heavy lifting. The description adds no meaning beyond it — it never explains what a "native identifier" is or how multiple IDs are resolved.

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

Purpose2/5

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

"Get native multiple-version metadata" pairs a verb with a resource, but "native" and "multiple-version" are undefined jargon and the definition never distinguishes its scope from siblings such as modrinth_file_versions or modrinth_project_versions. An agent cannot tell which version-listing tool this is without guessing from the name alone.

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 when-to-use guidance, no statement of which identifiers are expected, and no exclusion or pointer to the alternative version tools. The only routing hint is the deferred "endpoint reference", which is not supplied here.

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