Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

modrinth_collections

Resolve public Modrinth collections from a JSON array of base62 collection IDs, returning per-collection project-ID lists in the original order while excluding owner and private data.

Instructions

Resolve public Modrinth collections. Uses the native bulk read for a JSON array of collection IDs. Preserves the returned order, omissions and complete per-collection project-ID lists. Excludes owner account identifiers and private data. An empty array returns an empty array.

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_collections"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesNative JSON array of base62 collection IDs; [] is valid

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the behavioral burden and does well: it discloses order preservation, omission preservation, complete project-ID lists, exclusion of owner identifiers and private data, and empty-array behavior. It still omits error behavior, partial-failure semantics, and any rate-limit or authentication 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?

The definition is front-loaded and appropriately sized: purpose first, then input mechanism, then output guarantees and exclusions. Each sentence contributes useful information, with only minor overlap between the opening purpose and the bulk-read sentence.

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

Completeness4/5

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

For a one-parameter bulk lookup with no output schema and no annotations, the description covers the important behavioral details: ordering, omissions, project-ID completeness, privacy exclusions, and empty-array handling. Remaining gaps around error handling and exact response shape are minor but real.

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 schema already documents the single ids parameter as a native JSON array of base62 collection IDs with [] as valid input. The description reinforces that it expects a JSON array but does not add syntax or semantic detail beyond the schema.

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 description states a specific verb and resource: 'Resolve public Modrinth collections,' and clarifies that it operates on a JSON array of IDs via a bulk read. This makes the plural/bulk scope clear, though it does not explicitly name the singular sibling tool as the alternative for single-collection retrieval.

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 usage for bulk collection resolution from an array of IDs, and notes that an empty array is valid. However, it does not explicitly state when to use this tool versus the singular modrinth_collection sibling or any other alternative.

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