Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

modrinth_metadata_loaders

Retrieve Modrinth loader capabilities, including native v3 loader names, supported games, project types, fields, and metadata; use dedicated loader-field discovery to find accepted field names.

Instructions

Get Modrinth loader capabilities. Returns native v3 loader names, supported games, project types, supported fields and metadata. Use the dedicated loader-field discovery to obtain accepted field names.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it does describe the return payload contents, which is the main behavioral fact for a stateless read. It says nothing about caching, ordering, rate limits, or whether the catalog is static, so the disclosure is informative but not complete for a tool with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the purpose, followed by the payload and then the routing hint. Nothing is padded, and each sentence adds a distinct fact. The slightly loose 'supported fields and metadata' phrase is the only soft spot.

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 parameterless, annotation-free, read-only catalog lookup with no output schema, the description covers purpose, payload shape, and a cross-tool pointer. Missing only operational detail such as whether the result is stable or cached, which is minor at this complexity.

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 no parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The pointer to a separate loader-field discovery tool is a useful adjacent clarification but not parameter semantics.

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?

A specific verb plus resource: 'Get Modrinth loader capabilities,' immediately narrowed by an enumeration of what comes back (native v3 loader names, supported games, project types, supported fields). It is clearly a reference-data lookup rather than a project/version query, though it never names the sibling tool that returns the underlying loader data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a positive trigger (fetch loader capabilities) and explicitly routes the agent elsewhere for a related need: 'Use the dedicated loader-field discovery to obtain accepted field names.' That implicitly distinguishes it from the loader-field tools. It stops short of stating exclusions, e.g. that this tool does not return the values of a given field.

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