Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

modrinth_organization

Read a public Modrinth organization by ID or slug to return its name, description, and icon metadata while excluding private account, team, and moderation data.

Instructions

Read a public Modrinth organization. Reads an organization by its native ID or slug and returns its public name, description and icon metadata. Account, team-member and moderation data are excluded.

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

Name	Required	Description	Default
`id`	Yes	Organization ID or slug from a public organization URL or project metadata

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

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 useful work: it scopes the tool to public organizations, enumerates what is returned (name, description, icon metadata), and explicitly excludes account, team-member, and moderation data. It is slightly thin on what happens for invalid, private, or nonexistent slugs, which is the main remaining gap.

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?

Three short sentences, front-loaded with the core action and immediately followed by the return scope and exclusions. The opening 'Read a public Modrinth organization' is partially redundant with 'Reads an organization by its native ID or slug', costing one sentence of efficiency.

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?

For a one-parameter read tool with no output schema, the definition covers the essentials: input form, returned fields, and explicitly excluded sensitive data. Error behavior for private or unknown organizations is the only notable omission.

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 is already documented as 'Organization ID or slug from a public organization URL or project metadata'. The description restates this as 'native ID or slug' without adding syntax, format, or resolution behavior beyond the schema, so the baseline of 3 applies.

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 and resource: 'Read a public Modrinth organization' and 'Reads an organization by its native ID or slug'. This makes it a single-item getter, distinguishable by implication from the plural sibling modrinth_organizations and from modrinth_organization_projects, though no sibling is explicitly named.

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 only implied by 'Read a public Modrinth organization' – it's inferable that this is for fetching a single org's details. There is no explicit when-to-use guidance, no exclusion pointing at modrinth_organizations for listing or modrinth_organization_projects for related data.

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

Deploy Server