Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

modrinth_organization_projects

Retrieve all publicly visible Modrinth projects for a given organization ID or slug, returning native order and reviewed metadata without filters, sorting, or pagination.

Instructions

Read a public organization's Modrinth projects. Returns every anonymously visible project published by the organization in native order, including reviewed game, compatibility and public server metadata. Validates organization identity before accepting the list. Does not add project-type filters, sorting or pagination.

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

Input Schema

NameRequiredDescriptionDefault
idYesOrganization ID or slug from a public organization URL or project metadata

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 supplied, the description carries the full burden and does well: it discloses the visibility scope ('every anonymously visible project'), the ordering ('native order'), the metadata included, and the validation behavior on the identifier. It stops short of describing the failure mode for an invalid or private organization or any rate limits.

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 purpose and scoping constraints before the negative exclusions. Little waste, though 'Validates organization identity before accepting the list' is slightly abstract phrasing that could be tightened.

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 single-parameter read tool with no output schema, the definition covers visibility, ordering, included metadata, and the absence of filtering/pagination. What remains missing is minor: the error behavior for an invalid or non-public organization.

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% and there is only one parameter, so the schema already documents that 'id' accepts an organization ID or slug. The description adds only that the organization must be public and that its identity is validated, which is marginal but relevant context.

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: 'Read a public organization's Modrinth projects.' The qualifier 'organization's' separates it from the broader project-listing siblings, though no sibling is named directly.

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?

The closing sentence ('Does not add project-type filters, sorting or pagination') implies an agent should look elsewhere when filtering or paging is needed, but it never names the alternative tool or states a positive when-to-use condition beyond 'public organization'.

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