Crawlora MCP

modrinth_dependencies

Read-only

Get a Modrinth project's dependency graph and return its native projects and versions arrays: each dependency's project id, version id, dependency type (required, optional, incompatible or embedded) and the files that satisfy it. Use modrinth_project first to read the project itself; this endpoint returns dependency references only, never dependency file contents.

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

Input Schema

Name	Required	Description	Default
`id`	Yes	Required Modrinth project id or slug, for example AANobbMI or sodium.

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

A4.2/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 known. The description adds genuinely useful behavior: the response is the native projects/versions arrays, the four dependency-type values are enumerated, and it clarifies the result is references rather than downloadable file contents — a real boundary an agent could otherwise mis-assume.

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 action and followed by the disambiguation, with no filler. The first sentence is dense with enumerated fields but each clause carries information; only minor tightening would improve it.

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?

For a single-parameter read tool with an output schema and annotations already supplied, the description covers what remains: the shape of the result, the meaning of the dependency-type values, the reference-only limitation, and the sibling to use for project details. Nothing needed to call it correctly is missing.

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% with a single required id, and the schema already documents that it accepts a project id or slug with examples. The description only alludes to "a Modrinth project's" and adds no format or edge-case detail beyond the schema, so the 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 a Modrinth project's dependency graph") and enumerates what comes back: projects and versions arrays with project id, version id, dependency type, and satisfying files. It explicitly distinguishes itself from modrinth_project, so an agent can tell the two apart without opening either schema.

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?

Gives a clear routing instruction ("Use modrinth_project first to read the project itself") and a scope exclusion ("dependency references only, never dependency file contents"). It stops short of naming when to prefer version- or file-oriented siblings such as modrinth_project_version or modrinth_version, but the primary alternative is covered.

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.