Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

modrinth_project

Read-only

Get one Modrinth project by id or slug and return its native public metadata: id, slug, title, description, project type, client and server side types, categories, loaders, game versions, license, download and follow counters, source and wiki links, gallery images, featured versions and donation URLs. Use modrinth_search or modrinth_projects to find an id; this read never returns account, payout or moderation data.

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

Input Schema

NameRequiredDescriptionDefault
idYesRequired Modrinth project id or slug, for example AANobbMI or sodium.

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.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds a meaningful scope boundary: the response never includes account, payout, or moderation data. That tells the agent not to reach for this tool when it needs private or administrative fields, which the annotations alone would not convey.

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?

Front-loaded with the action, followed by the routing hint and the data-scope caveat, which are the two highest-value sentences. The long enumeration of returned fields overlaps with the output schema and could be trimmed without losing guidance.

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?

The tool is simple (one parameter), annotations cover the safety profile, and an output schema exists, so return values need no explanation here. The description fills the remaining gaps: how to obtain an id and what data is out of scope.

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?

With 100% schema description coverage, the single parameter is already fully documented including a concrete example. The description's 'id or slug' phrasing restates the schema rather than adding new meaning, so baseline 3 applies.

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?

States a specific verb and resource ('Get one Modrinth project by id or slug') and enumerates the returned metadata, so an agent knows exactly what this retrieves. It is clearly distinguishable from the search/list siblings by the singular-project scope.

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?

Explicitly routes the agent to modrinth_search or modrinth_projects when it needs to resolve an id first, which is the main failure mode for this tool. It does not address other adjacent siblings, but the core when-to-use guidance is clear and actionable.

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