Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

modrinth_metadata_loader_fields

Discover supported Modrinth loader fields from the native loader catalog, preserving first-source order and refreshing names as the catalog changes.

Instructions

Discover Modrinth loader fields. Returns every distinct supported field advertised by the native loader catalog, preserving first source occurrence. Names refresh with the loader catalog rather than a hard-coded field list.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

B3.3/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 load. It does disclose real behavior: deduplication ('every distinct'), ordering ('preserving first source occurrence'), and that the set is dynamic ('names refresh with the loader catalog rather than a hard-coded field list'). It says nothing about cost, caching, auth, or the concrete shape of the returned items, which leaves meaningful gaps for a no-annotation tool.

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 short sentences, front-loaded with the purpose, then two sentences of behavioral detail. 'Preserving first source occurrence' is terse and slightly jargon-y, but it is information-dense rather than filler, and nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a trivial zero-parameter enumeration tool with no output schema, the description covers what is returned conceptually (distinct supported field names) and why it changes over time. However, with no output schema the description should pin down the concrete return shape (bare strings vs. field objects) and it does not, so an agent cannot fully anticipate the response.

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, which is the baseline-4 case; there is nothing for the description to disambiguate. The description correctly implies no input is required by framing the call as a catalog discovery.

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?

States a specific verb+resource ('Discover Modrinth loader fields') and the second sentence clarifies that it returns the full distinct set of supported field names rather than values. It is clear enough to separate from a value-lookup tool, though the term 'field' is never defined, so an agent must infer it means loader attribute names.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no mention of alternatives such as the sibling that returns field values or the loaders list. The word 'Discover' weakly implies it is a catalog-introspection call, but nothing tells the agent when this tool is the right choice versus those siblings.

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