Crawlora MCP

modrinth_organizations

Read-only

Resolve a JSON array of public Modrinth organization IDs or slugs in one native bulk read and return the public organization records (id, slug, name, description, icon URLs and color). Send exactly one ids array parameter; an empty array is valid. The response preserves the source's returned order and omissions: duplicate requests may resolve to one row, unknown IDs are omitted, and no placeholder is synthesized or local reordering applied. Members, account identifiers and moderation metadata are excluded; malformed input is rejected.

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": {
      "ids": "<ids>"
    },
    "name": "modrinth_organizations"
  }
}

Input Schema

Name	Required	Description	Default
`ids`	Yes	Required JSON-encoded array of native organization IDs or slugs, for example ["tREwurHE","ModLabs"]. An empty array is valid. This is one native bulk read: unknown IDs are omitted, output order is not reordered to match the input, and no placeholders are synthesized.

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.1/5.0

Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses concrete behavior: duplicate requests may collapse to one row, unknown IDs are omitted, no placeholders are synthesized, and output order is the source's rather than the input's. It also names what is excluded (members, account identifiers, moderation metadata), which is exactly the kind of detail annotations cannot 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?

The paragraph is dense and front-loaded, leading with the action and the calling contract before the edge-case semantics. It loses a mark for repeating the order/omission/no-placeholder rules that the parameter schema already spells out, making parts of it redundant rather than additive.

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 safety annotations, everything an agent needs is present: input format, empty-array validity, omission and ordering behavior, excluded fields, and error handling. Nothing material is left unstated.

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 is already high, and the description still adds meaning: the array is JSON-encoded, slugs are acceptable in addition to native IDs, and an empty array is valid. It largely restates the duplicate/order semantics also present in the parameter description, so the marginal gain is modest.

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 opens with a specific verb and resource ('Resolve a JSON array of public Modrinth organization IDs or slugs') and frames it as a 'native bulk read', which implicitly separates it from the singular modrinth_organization sibling. It stops short of naming that alternative explicitly, keeping it just below the top mark.

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

Usage Guidelines3/5

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

It tells the agent how to invoke the tool ('Send exactly one ids array parameter; an empty array is valid') and that malformed input is rejected, giving practical calling guidance. However, it never states when to prefer this bulk read over modrinth_organization or modrinth_organization_projects, so selection against siblings is left to inference.

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.