Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

modrinth_check_project

Resolve a Modrinth project ID or slug to fetch its public metadata, helping you verify and identify the correct project before use.

Instructions

Resolve a project ID or slug. 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_check_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesNative id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

C2.9/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 behavioral burden but discloses little. It implies a public read operation by saying 'native public Modrinth metadata,' yet does not state authentication needs, rate limits, error behavior, or whether the operation is purely read-only.

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 core purpose and return value are front-loaded in two short sentences. The final sentence pointing to an endpoint reference is somewhat filler, but it does not obscure the main instruction.

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

Completeness3/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 with no output schema or annotations, the description gives an adequate high-level result but leaves the return shape, error handling, and sibling distinction implicit. It is usable but not fully self-contained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 100% description coverage but only labels the parameter as 'Native id.' The description adds useful meaning by stating that a project ID or slug is accepted, which expands on the schema's narrower phrasing.

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 states a specific verb and resource ('Resolve a project ID or slug') and a result ('Returns the native public Modrinth metadata'). However, it does not explain how this differs from sibling tools like modrinth_project, and the name 'check_project' suggests validation or existence checking rather than plain retrieval.

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 guidance on when to use this tool versus modrinth_project or modrinth_projects, nor any stated exclusions or prerequisites. The instruction to 'See the endpoint reference' offloads context externally instead of helping an agent select this tool.

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