Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

modrinth_metadata_loader_field_values

Read-only

Get every native value and its metadata records for one Modrinth loader field discovered through modrinth_metadata_loader_fields. Use the field name from that discovery; null ordering, type and major values and an explicit major=false stay distinct from omission, and an unknown field name is rejected rather than guessed.

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": {
      "field": "<field>"
    },
    "name": "modrinth_metadata_loader_field_values"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldYesRequired loader field name returned by modrinth_metadata_loader_fields, for example game_versions or mrpack_loaders. Names are the native catalog's own lowercase tokens; an unknown name is rejected.

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

A4.4/5.0
Behavior5/5

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

The annotations establish that this is a read-only, open-world operation, but the description adds valuable behavioral detail beyond them: null ordering, type, and major values, plus explicit major=false, remain distinct from omission. It also discloses validation behavior by saying unknown field names are rejected rather than guessed.

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 definition is compact and front-loads the core action before stating prerequisites and edge-case semantics. The second sentence is dense, packing multiple null/omission distinctions into one clause, but those details are relevant and not padding.

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

Completeness5/5

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

For a one-parameter read-only tool with an output schema, the description covers the important gaps: where the field name comes from, that every native value and metadata record is returned, how null and false values differ from omission, and that unknown names are rejected.

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%, and the single field parameter is already documented as required, sourced from modrinth_metadata_loader_fields, and rejected when unknown. The description reinforces that meaning but adds little beyond the schema baseline.

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 uses a specific verb and resource: it gets every native value and metadata records for one Modrinth loader field. It also distinguishes this from the discovery sibling by requiring the field name to come from modrinth_metadata_loader_fields.

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?

It clearly states the prerequisite: use a field name discovered through modrinth_metadata_loader_fields, and unknown names are rejected. It does not explicitly describe when not to use this tool or compare it to other metadata tools, but the dependency on discovery is clear.

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