Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

modrinth_project_disclosures

Fetches all public Modrinth project disclosures, including declaration types, fields, and timestamps for auditing project metadata without private or moderation controls.

Instructions

Get Modrinth public project disclosures. Returns all current public declarations, their type-specific fields and timestamps. Empty declarations are valid. Public AI/system/telemetry/derivative/paid-feature/archive metadata is preserved; moderation, authorship, lock and deletion controls are omitted. No credentials, private/member view or write operation is used.

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

Input Schema

NameRequiredDescriptionDefault
idYesNative project ID or canonical slug

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 it does so well: it declares the operation read-only, public-only, and credential-free, and it enumerates what is preserved (AI/system/telemetry/derivative/paid-feature/archive metadata) versus omitted (moderation, authorship, lock, deletion controls). It omits rate limiting and any notes on caching or freshness, which keeps it short of 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 core action and immediately followed by the return-shape summary, then the scope boundaries. The preserved/omitted clause is dense but every element is meaningful; no sentence is filler.

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?

Because there is no output schema, the description must describe returns itself, and it does: all current public declarations plus type-specific fields and timestamps, with an explicit note that empty declarations are valid. The residual gap is that 'type-specific fields' remains unspecified in shape, so an agent cannot predict concrete field names.

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?

There is a single required parameter with 100% schema description coverage ('Native project ID or canonical slug'), so the schema already does the explanatory work. The description adds nothing about how 'id' is resolved, whether invalid IDs error or return empty, which is the baseline for a fully documented schema.

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: 'Get Modrinth public project disclosures', and it further narrows the scope to 'all current public declarations'. That is enough for an agent to distinguish it from modrinth_project or modrinth_check_project, but it never names a sibling or states explicitly how it differs from the broader project metadata tool.

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 rather than stated: an agent can infer that this tool retrieves disclosure/declaration data for one project rather than full project metadata. There is no explicit 'use this when...' clause, no exclusion such as 'for license or loader data use modrinth_project instead', and no prerequisites for calling it.

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