Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

modrinth_metadata_loader_field_values

Retrieve all native enumerable values and metadata for a Modrinth loader field to inspect valid options while keeping null, ordering, type, major, and explicit false values distinct.

Instructions

Get Modrinth loader-field values. Returns all native enumerable values and metadata for a field from loader-field discovery. Null ordering/type/major and explicit false remain distinct; optional upstream metadata filters are not exposed.

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
fieldYesSource field name from loader-field discovery

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations the description carries the full burden, and it does meaningful work: it discloses that all native enumerable values are returned, that null ordering/type/major and explicit false remain distinct (a real edge-case a caller would otherwise get wrong), and that optional upstream metadata filters are not exposed. Auth, rate limits, and failure modes are not covered.

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 with the core purpose front-loaded and zero filler, though the clause on null ordering/type/major is jargon-dense and would benefit from a brief gloss.

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 one-parameter, no-output-schema read tool, the description covers purpose, return shape, and a scope limitation. The main residual gap is where valid field names come from and whether any permissions or rate limits apply.

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 parameter is already documented as the source field name from loader-field discovery, so the description repeats rather than extends it. Baseline 3 applies; no format examples or valid-name hints are added.

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 and resource ("Get Modrinth loader-field values") and clarifies it returns enumerable values plus metadata for one field, which separates it from the plural sibling modrinth_metadata_loader_fields. It does not explicitly name that sibling, so differentiation is inferable rather than stated.

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?

The phrase "from loader-field discovery" implies a prerequisite on the discovery tool and there is a clear implied context (resolving valid values for one field), but there is no explicit when-to-use / when-not-to-use guidance and no named alternative.

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