Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

modrinth_projects

Fetch native public metadata for multiple Modrinth projects in one request by passing a JSON-encoded array of project IDs.

Instructions

Get native multiple-project 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_projects"
  }
}

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.4/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden, yet it discloses nothing about authentication requirements, rate limits, behavior for unknown or unpublished project IDs, or any cap on how many IDs may be supplied. The final sentence defers all real behavioral detail to an external "endpoint reference" instead of stating it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences where the second ("Returns the native public Modrinth metadata for this resource") largely restates the first, and the third is a pointer elsewhere rather than information. The only useful content is the opening phrase, so the text does not earn its length.

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 batch metadata tool with no output schema and no annotations, the agent needs to know the return shape, batching limits, and error semantics; all are absent or outsourced to an external reference. The one input parameter is documented by the schema, but that is not enough for correct invocation.

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 being skipped. The description adds no syntax example, size limit, or ordering guarantee beyond that, so the baseline 3 applies.

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?

"Get native multiple-project metadata" names a verb and a resource, and "multiple-project" hints at a batch fetch versus the singular modrinth_project sibling, but "native" and "this resource" are unexplained jargon, so the agent cannot tell precisely what metadata is returned. The core intent is guessable but not crisp.

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 and no routing to alternatives, despite many sibling tools that also fetch project data (modrinth_project, modrinth_search, modrinth_project_versions). Nothing tells the agent when a batched multi-project lookup is preferable to a single-project call or a search.

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