Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

modrinth_organization

Read-only

Read one public Modrinth organization by native ID or slug and return its id, slug, name, description, nullable icon_url, raw_icon_url and color. Slugs may contain letters, digits, dots, underscores and hyphens and keep their source spelling. Use this to resolve an organization from a public organization URL or from project/search metadata before reading its projects. Team IDs, member profiles, account data and moderation notes are excluded; invalid identifiers are rejected and unavailable organizations return not found.

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

Input Schema

NameRequiredDescriptionDefault
idYesRequired native organization ID or slug from a public organization URL or from project/search metadata, for example tREwurHE or ModLabs. Slugs may contain letters, digits, dots, underscores and hyphens; the source spelling is preserved.

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/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and reach are covered. The description adds real context beyond that – which data classes are excluded (team IDs, member profiles, account data, moderation notes) and the two failure modes (invalid identifier rejected, unavailable org returns not found). It loses credit for enumerating return fields that the output schema already carries.

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?

Front-loaded with the verb, resource and identity key, then usage, then boundaries and errors – a sensible ordering with no filler sentences. It does repeat the return-field list and slug character set already present in the structured schema, which is wasted space.

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 full annotation and output-schema coverage, the description supplies everything an agent needs: what is returned, what is deliberately not returned, when to call it, and how failures surface. No behavioral gap remains that would cause a mis-call.

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 description coverage is 100% and the single parameter's own description already states the ID/slug rules, the allowed character set and the preserved spelling. The description restates the same slug constraints rather than adding new meaning such as lookup precedence or malformed-input behavior specific to each form.

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?

Names a specific verb and resource ("Read one public Modrinth organization") plus the lookup key (native ID or slug), and 'one public' scopes it against the plural listing sibling without having to name it. An agent can immediately tell it apart from modrinth_organizations and modrinth_organization_projects.

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 concrete use case: resolve an organization from a public organization URL or from project/search metadata, and explicitly frames it as a prerequisite step before reading its projects, which routes the agent onward. What is missing is an explicit exclusion (e.g. when to use the list endpoint instead), so it stops short of a 5.

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