Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

modrinth_organizations

Resolve public Modrinth organizations from IDs or slugs in bulk, preserving order and omissions while returning metadata without members or account data.

Instructions

Resolve public Modrinth organizations. Uses the native bulk read for a JSON array of organization IDs or slugs. Preserves native response order and omissions instead of creating entries for unknown IDs. Returns public organization metadata without members or account data. An empty array returns an empty array.

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

NameRequiredDescriptionDefault
idsYesNative JSON array of organization IDs or slugs; [] is valid

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses order preservation, that unknown IDs are omitted rather than materialized as entries, that only public metadata is returned (no members or account data), and that an empty array yields an empty array. It does not address authentication needs or failure behavior for malformed arrays, which keeps it below a 5.

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?

Four short sentences, front-loaded with the action and then the edge-case semantics (order, omissions, empty array), each contributing something. Slightly dense but no filler sentences.

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

Completeness4/5

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

No output schema exists, so the description must convey return shape, and it does explain what comes back (public organization metadata, order preserved, unknown IDs omitted). Given a one-parameter, non-destructive read tool, that is close to sufficient, though return field detail and error semantics are absent.

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 parameter already documented as a native JSON array of IDs or slugs where [] is valid, so the description adds essentially no syntax or format meaning beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb ('Resolve') and resource ('public Modrinth organizations') and immediately clarifies that it is a bulk read over an array of IDs or slugs, which implicitly separates it from the singular modrinth_organization sibling. It stops short of naming the single-item alternative explicitly, so an agent must infer the pairing.

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?

Usage is implied by 'native bulk read for a JSON array' — an agent can infer this is for multiple lookups at once — but the description never says when to prefer this over modrinth_organization or modrinth_organization_projects, and offers no prerequisites or exclusions.

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

Deploy Server

Other Tools