Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

modrinth_check_project

Read-only

Resolve a Modrinth project id or slug to the project's own native check object, which carries its id and the site's validation fields, without returning the full project detail. Use this when you only need to confirm that an id or slug exists; a missing project returns 404.

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_check_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.3/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 safety profile is covered. The description adds useful behavioral context beyond that: the missing-project case returns 404, and the return payload is a lightweight check object with id and validation fields rather than the full project record. It does not mention rate limits or the shape of the validation fields, but the output schema exists for that.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with no waste. The core verb and scope come first, followed by the selecting condition and the error behavior. Every clause carries information an agent would otherwise have to infer.

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?

This is a single-parameter read tool with a full schema, an output schema, and annotations covering safety and open-world behavior. The description supplies purpose, when to use it, and the failure mode, which is everything an agent needs beyond the structured fields.

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 coverage is 100% and the single parameter already documents that it accepts a project id or slug, including the examples AANobbMI and sodium. The description repeats the 'id or slug' idea without adding format rules, casing expectations, or edge cases. Baseline 3 is appropriate when the schema fully documents the only parameter.

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 combination: 'Resolve a Modrinth project id or slug to the project's own native check object.' It distinguishes this from the full-detail sibling by explicitly stating 'without returning the full project detail,' so an agent can separate this narrow existence check from a general project lookup.

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 gives explicit positive guidance: 'Use this when you only need to confirm that an id or slug exists.' That is a clear selection rule against doing a heavier lookup. It does not name the alternative tool to use when full details are needed, but the phrase 'without returning the full project detail' implies it.

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