Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

modrinth_search_v3_body

Search Modrinth via its native v3 JSON request body, controlling query, filters, facets, index, offset, limit, and optional metadata without modifying projects or account state.

Instructions

Search Modrinth using the native v3 JSON body. Performs the upstream native POST search read. Offset and limit are decimal strings in this body; show_metadata preserves explicit false and optionally returns native per-hit score/sort metadata. No projects or account state are modified. Other fields and filter precedence match GET search.

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": {
      "body": "<body>"
    },
    "name": "modrinth_search_v3_body"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesNative search body; offset/limit are strings

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

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 does real work: it states 'No projects or account state are modified' (read-only contract) and describes return-side behavior for show_metadata, including that explicit false is preserved. It omits pagination defaults, limits beyond the string typing, and auth/rate-limit context, so it is strong but not exhaustive.

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?

Four short sentences, front-loaded with the core action and followed by the quirks most likely to cause a bad call. No filler, though 'Performs the upstream native POST search read' is somewhat redundant with the first sentence.

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 nested-body read tool with no output schema and no annotations, the description covers the read-only guarantee, the string-typed pagination quirk, and metadata return behavior, and it points to GET search for the remaining field semantics. An agent could call it correctly, though the unlisted body fields (index, facets, filters, version) rely on external documentation.

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 baseline is 3, but the description adds genuine meaning beyond the schema by specifying that offset and limit are 'decimal strings' and by explaining the false-preserving semantics of show_metadata, neither of which the schema states. It still defers all other body fields to the GET search docs.

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 description names a specific verb and resource ('Search Modrinth using the native v3 JSON body') and clarifies the transport ('upstream native POST search read'), which separates it from the query-string variants. It stops short of naming the sibling tool (e.g. modrinth_search_v3) that an agent should pick instead, so differentiation is implied rather than explicit.

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?

Usage is only implied through the closing line 'Other fields and filter precedence match GET search', which gestures at an alternative without stating when to choose this body-based variant over it. There are no explicit prerequisites, exclusions, or decision criteria for the agent.

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