Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

modrinth_search_v3_options

Discover Modrinth v3 search options, including supported indexes, server UI regions/languages, native filter expressions, disclosure flags, and catalog paths for dynamic project types.

Instructions

Discover Modrinth v3 search options. Returns all supported indexes, published server UI region/language choices, exact native content/status filter expressions, disclosure search flags and catalog paths for dynamic project types, categories, loaders, versions, environments and licenses. These reference choices do not restrict the native expression grammar.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full load. It conveys that this is a passive discovery tool returning catalog/reference data and that the listed choices are non-restrictive, which is meaningful behavioral context, but it says nothing about freshness, whether results are static, or any cost/rate considerations.

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?

Three sentences, front-loaded with the core purpose, followed by a return-value enumeration and one clarifying constraint. Dense but every sentence adds information; no filler or restatement of the name.

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?

There is no output schema and no annotations, so the description must explain what comes back, and it does enumerate the returned categories (indexes, regions/languages, filter expressions, flags, catalog paths). The one gap is the actual response shape/format, which is not described.

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 tool takes zero parameters, so there is no per-parameter semantics to explain; the baseline for a parameterless tool applies. The description appropriately spends its words on the return payload instead of inventing input details.

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 gives a specific verb and resource ("Discover Modrinth v3 search options") and immediately enumerates what the returned reference data covers: indexes, region/language choices, filter expressions, flags, and catalog paths. It is clearly a metadata/reference tool rather than a search executor, though it never names a sibling (e.g., modrinth_search_v3) to make the distinction 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: an agent can infer this should be consulted to learn valid filter values before running a search. The closing sentence usefully warns that the returned choices do not constrain the native expression grammar, but there is no explicit when-to-use/when-not statement or pointer to the actual search 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