Crawlora MCP

modrinth_forge_updates

Read-only

Get the Forge update metadata document for one Modrinth project and return its homepage plus the promos map of promoted version strings keyed by game version and loader. Pass neoforge=include to add NeoForge promotions or neoforge=only to return only those; omitting it keeps the native Forge default. This mirrors the legacy Forge update JSON consumed by launchers.

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": {
      "id": "<id>"
    },
    "name": "modrinth_forge_updates"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Required Modrinth project id or slug.
`neoforge`	No	Optional NeoForge selection: include or only. Omit it to keep the native Forge default.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 11, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description only needs to add context — which it does by describing the shape of the returned document (homepage plus a promos map keyed by game version and loader) and the conditional output when neoforge is set. It stops short of noting failure modes, such as a project with no Forge promotions.

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 action and return shape, then parameter behavior, then legacy-compatibility context. Every sentence carries information, though the schema already covers the neoforge default, making that sentence partly redundant.

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?

With only two fully documented parameters and an output schema present, the description covers everything needed to invoke the tool correctly and understand the response shape. Minor gaps are error/edge-case behavior for projects lacking Forge promotions.

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%, with both `id` and `neoforge` documented including the default behavior of omitting neoforge. The description's explanation of the two neoforge modes largely restates the schema, so it adds little new meaning to the parameters themselves.

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 names a specific verb and resource ('Get the Forge update metadata document for one Modrinth project') and states exactly what is returned ('homepage plus the promos map of promoted version strings keyed by game version and loader'). An agent can distinguish this from project/version metadata siblings without opening any schema.

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 guidance is limited to the neoforge parameter ('include' vs 'only' vs omit), not to when this tool should be chosen over modrinth_project, modrinth_project_version, or other metadata siblings. The 'mirrors the legacy Forge update JSON consumed by launchers' clause implies the use case but never states it as a selection rule.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

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.