Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

modrinth_license

Read-only

Get one license id's title and full license text from Modrinth's own tag catalog, matching the license attached to a project or version. Use the exact id from modrinth_tags with type=license; NOASSERTION returns an empty body by design, and this is license text only, not legal advice.

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

NameRequiredDescriptionDefault
idYesRequired exact license id from modrinth_tags with type=license, for example MIT. NOASSERTION returns an empty body by design.

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

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

Goes beyond the readOnly/openWorld annotations by disclosing two non-obvious behaviors: NOASSERTION returns an empty body by design (preventing a false failure diagnosis) and the output is license text only, not legal advice. The disclaimer and empty-body caveat are exactly the kind of context annotations cannot express.

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?

Two sentences, front-loaded with the purpose, with the id-sourcing rule and edge cases after it. Slightly dense with semicolons and repeated NOASSERTION wording that also appears in the schema, but no filler sentences.

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?

Single required parameter, full schema coverage, annotations present, and an output schema that covers return shape. The description supplies the remaining essentials — id provenance, empty-body behavior, and the not-legal-advice caveat — so an agent can call it correctly without further inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3; the description earns extra by explaining where the id comes from (modrinth_tags with type=license) and that it must match the license attached to a project or version. That provenance meaning is only partially present in the schema wording.

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 a single license id's title and full license text from Modrinth's tag catalog. It also scopes the resource as the license attached to a project or version, which distinguishes it from the catalog-listing sibling modrinth_tags.

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 directs the agent to source the id from modrinth_tags with type=license, which is the key routing rule, and warns that NOASSERTION is a legitimate empty-body case rather than an error. It does not name a when-not-to-use case, but the prerequisite guidance is concrete.

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