Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

modrinth_search_v3_body

Read-only

Search Modrinth with the native v3 JSON request body. Result and filter semantics match modrinth_search_v3, but offset and limit are decimal strings in this body and show_metadata preserves an explicit false while optionally returning native per-hit score and sort metadata. This is a read-only search: no project, account or listing state is modified.

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

Input Schema

NameRequiredDescriptionDefault
indexNoOptional native result order. Discover the accepted values with modrinth_search_v3_options.
limitNoOptional native limit as a decimal string, for example "100"; defaults to 10 and the source normalizes 0 to 1 and clamps values above 100.
queryNoOptional native search text.
facetsNoOptional legacy JSON array of string arrays using v3 field names. Numeric-looking version literals need the native quoting form.
offsetNoOptional native nonnegative offset as a decimal string, for example "100"; defaults to 0.
filtersNoOptional legacy filter-expression clause, combined with version using AND when new_filters is absent.
versionNoOptional legacy secondary filter-expression clause. This is not a bare game-version value.
new_filtersNoOptional current native filter expression, forwarded unchanged. When supplied it takes precedence over facets, filters and version.
show_metadataNoOptional native per-hit metadata switch. An explicit false is preserved and asserts that search_metadata is absent; true returns native score/sort metadata.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds useful behavioral nuance about decimal-string offset/limit handling, preservation of explicit false for show_metadata, and optional native per-hit metadata. It also reinforces that no project, account, or listing state is modified, though it does not discuss auth or rate limits.

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 description is front-loaded and compact, moving from the core action to sibling comparison to behavioral constraints. Every sentence contributes, though the dense phrasing around native metadata could be slightly easier to scan.

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 a nine-parameter search tool with full schema coverage and an output schema, the description covers the important distinctions and behavioral caveats. The main gap is that it does not explicitly state when to use this variant instead of modrinth_search_v3.

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 the schema already documents all nine parameters thoroughly. The description reinforces a few important semantics, such as offset and limit being decimal strings and new_filters taking precedence, but adds limited meaning beyond the schema itself.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: search Modrinth using the native v3 JSON request body. It also distinguishes this tool from the sibling by noting that result and filter semantics match modrinth_search_v3 while documenting body-specific differences.

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 implies this is the raw-body variant of modrinth_search_v3, but it never explicitly says when an agent should choose this tool over the sibling. It provides contextual contrast without a clear when-to-use or when-not-to-use rule.

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

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources