Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

modrinth_license

Retrieve a Modrinth resource's source license title and text by native ID, returning clean public metadata JSON for license verification.

Instructions

Get source license title and text. Returns the native public Modrinth metadata for this resource. See the endpoint reference for exact request and response behavior.

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

Input Schema

Name	Required	Description	Default
`id`	Yes	Native id

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden. "Get" implies a read, but nothing states whether the call is authenticated, whether licenses are cached or public, or what errors look like; "native public Modrinth metadata" is the only substantive behavioral clue.

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

Conciseness3/5

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

Two sentences are informative and front-loaded, but the third ("See the endpoint reference for exact request and response behavior") is boilerplate that offloads the description's job to an external document.

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

Completeness3/5

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

For a simple single-parameter read tool with no output schema, the description should at least sketch the return shape; "title and text" does so minimally, but the deferral to an endpoint reference leaves request/response behavior unspecified in the definition itself.

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% for the single required param, so the baseline is 3. The description adds nothing about what the "Native id" refers to (license id versus project or version id), leaving a real ambiguity the schema does not resolve beyond the tool name.

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?

The description names a specific verb and resource: get the source license title and text. That is enough for an agent to know it returns license content rather than project or version data, though it never explicitly contrasts itself with the many project/version siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to call this versus other metadata tools, no stated prerequisites, and no mention of what happens if the id is invalid. The only routing hint is a generic pointer to an external endpoint reference, which does not help an agent decide at selection time.

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

Deploy Server