Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

modrinth_project

Retrieve public Modrinth project metadata by native ID, returning clean JSON details for a resource. Use it to look up project information directly from Modrinth.

Instructions

Get a Modrinth project. 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": {
      "id": "<id>"
    },
    "name": "modrinth_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesNative id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

C2.5/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. It implies a read of public metadata, but discloses nothing about authentication requirements, rate limits, error behavior on unknown ids, or what the returned metadata contains, deferring instead to an unspecified external endpoint reference.

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 with the core purpose, which is good. But the final sentence about the endpoint reference is a low-value deflection that displaces information the agent actually needs, so not every sentence earns its 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 single-parameter lookup tool with no annotations and no output schema, the description should at least summarize the returned fields or identifier format. Instead it outsources both request and response semantics to an external reference the agent cannot consult, leaving the definition under-specified.

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?

There is a single required parameter with 100% schema description coverage, so the schema already documents it and the baseline of 3 applies. The description adds no meaning beyond the schema — notably it never explains which identifier namespace "native id" refers to (project slug vs. project ID).

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?

The description names a specific verb and resource ("Get a Modrinth project") and says it returns native public Modrinth metadata, which is clearer than a bare restatement. However, it offers no differentiation from closely related siblings such as modrinth_check_project, modrinth_projects, or modrinth_project_versions, so an agent cannot tell from the text which one retrieves full project metadata.

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 conditions or prerequisites, and no mention of alternatives. The only routing advice is "See the endpoint reference", which is not usage guidance for selecting this tool over its siblings.

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