Crawlora MCP

Official

by Crawlora-org

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

modrinth_search

Search Modrinth projects by query, facets, sort order, and pagination to retrieve public project metadata as JSON.

Instructions

Search Modrinth projects. Returns the native public Modrinth metadata for this resource. See the endpoint reference for exact request and response behavior.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "modrinth_search"
  }
}

Input Schema

Name	Required	Description
`index`	No	Native search order
`limit`	No	Native result limit, zero to 100
`query`	No	Search text
`facets`	No	Native JSON array of OR groups joined by AND; see the full facet reference
`offset`	No	Native result offset, at least zero

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

C2.8/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, yet it only says it returns 'native public Modrinth metadata' and defers to an external endpoint reference that the agent may not have. It does not disclose pagination behavior, result ordering defaults, rate limits, or whether authentication is needed.

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?

The opening sentence is well front-loaded, but the two trailing sentences are boilerplate deferral ('See the endpoint reference...') that convey little operational value. It is short, but part of its length does not earn 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 five-parameter search tool with no annotations and no output schema, the description should explain result shape and pagination semantics; instead it offloads that to an unavailable endpoint reference. An agent cannot determine how to page through results or how facets interact with query from this text alone.

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 description coverage is 100%, so every parameter (index, limit, query, facets, offset) is already documented in the schema, including the enum values. The description adds no meaning 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.

Purpose4/5

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

States a concrete verb and resource: 'Search Modrinth projects.' An agent immediately knows the operation, but nothing distinguishes it from the numerous similarly named siblings (modrinth_search_v3, modrinth_search_v3_body, modrinth_search_v3_options).

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?

No when-to-use guidance, no prerequisites, and no mention of alternatives despite several near-identical search siblings. Usage must be inferred entirely from the verb 'search' and the generic project scope.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server