Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

modrinth_random_projects

Retrieve a set number of random public Modrinth projects with native metadata. Use it to discover varied project data for browsing or sampling.

Instructions

Get native random projects. Returns the native public Modrinth metadata for this resource. See the endpoint reference for exact request and response behavior.

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": {
      "count": "<count>"
    },
    "name": "modrinth_random_projects"
  }
}

Input Schema

NameRequiredDescriptionDefault
countYesNumber of random projects, 1 to 100

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

C2.5/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It states only that public metadata is returned and then defers behavior to an external "endpoint reference," leaving unaddressed whether the sample is with or without replacement, whether it is deterministic, auth requirements, or 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loads the action, which is good. But the third sentence ("See the endpoint reference for exact request and response behavior") is a pointer that consumes space without conveying information the agent can act on.

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

Completeness2/5

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

The tool is simple (one bounded integer parameter, no output schema), so completeness is achievable, yet the description omits what a "random project" sample means and outsources all request/response detail. An agent could call it, but not predict the shape or properties of the result.

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 ("Number of random projects, 1 to 100"), so the schema already fully documents it. The description adds no further meaning beyond confirming randomness, which is the baseline expectation when the schema does the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Get native random projects" names a verb and resource, so the basic action (fetch a random sample of projects) is inferable. However, "native" is undefined jargon, and nothing distinguishes this from siblings such as modrinth_projects or modrinth_search, which an agent could easily confuse it with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool versus the many sibling project-listing and search tools, and no exclusions or prerequisites. The agent must guess that this is for random sampling rather than filtered or paged listing.

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