Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

modrinth_search_v3

Search current Modrinth projects and servers with native v3 filters, sorting, pagination, and version-aware results to find matching listings.

Instructions

Search current Modrinth projects and servers. Returns native v3 name/summary/project_types/version-aware hits, page, hits_per_page and total_hits. Uses native offset/limit and filter expressions unchanged. Source limit0 resolves to1, values above100 cap at100; page is one-based. New_filters takes precedence over legacy filters/version; version is a legacy expression clause, not a bare game-version value. Use search options and native metadata catalogs for values.

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

Input Schema

Name	Required	Description
`index`	No	Native v3 order
`limit`	No	Native nonnegative limit; default10; source normalizes to1–100
`query`	No	Native search text
`facets`	No	Legacy JSON array of string arrays using v3 field names
`offset`	No	Native nonnegative offset; default0
`filters`	No	Legacy filter-expression clause
`version`	No	Legacy secondary filter-expression clause
`new_filters`	No	Native current filter expression, forwarded unchanged

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A3.8/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 full burden and does well: it discloses the return shape (name/summary/project_types/version-aware hits, page, hits_per_page, total_hits), the limit normalization (0→1, >100 caps at 100), one-based paging, and filter precedence. It omits auth requirements and rate limits, but the behavioral core is well covered.

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?

Purpose is front-loaded, followed by return shape and then constraints, with no filler wording. It is dense and somewhat run-on in the middle, but every clause (limits, paging, precedence, version semantics) carries information an agent needs.

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 an 8-parameter tool with no annotations and no output schema, the definition supplies return fields, limit behavior, paging base, and filter precedence, which covers what an agent needs to call it correctly. Minor gaps remain around defaults when neither filter style is supplied, but overall it is complete.

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?

Schema coverage is 100%, so the baseline would be 3, but the description adds meaning beyond the schema by stating that new_filters overrides legacy filters/version and that version is a legacy expression clause rather than a bare game-version value. These clarifications resolve ambiguity the schema alone would leave.

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 first sentence states a specific verb (Search) and resource (Modrinth projects and servers), and the 'v3' / native terminology distinguishes it from the legacy modrinth_search sibling. It does not explicitly name that sibling, but the resource and native-v3 framing make the tool's role clear.

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 gives precedence rules ('New_filters takes precedence over legacy filters/version') and points to search options and metadata catalogs for values, which implies usage context. However, it never explicitly says when to choose this over modrinth_search or modrinth_search_v3_options, leaving the main selection decision to inference.

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

Deploy Server