Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

modrinth_random_projects

Read-only

List one to one hundred random public Modrinth projects with the same native project metadata rows as modrinth_projects. Use this for sampling or discovery when no search term applies; the set is chosen by the upstream on each call, so results are not stable between requests.

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
countYesRequired number of random projects, from 1 to 100.

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.3/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses that the sample is chosen upstream on every call and that results are not stable between requests, which is exactly the non-determinism an agent needs to plan around. It does not discuss pagination or cost, but for a single-call sampling tool that is a minor gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Two sentences, both front-loaded with the essential information: what it returns first, then when to use it and the instability caveat. No filler or redundant restatement of the tool name.

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 one-parameter, read-only sampling tool with an output schema and annotations, the description covers scope, output shape reference, usage condition, and result instability. Nothing an agent needs to call it correctly is missing.

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 the single count parameter already documents its 1-100 range, so the description's 'one to one hundred' only restates the schema. No added meaning about ordering, error behavior, or count boundaries relative to the upstream limits.

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?

States a specific verb (list), resource (random public Modrinth projects), and explicit bound (one to one hundred), and anchors the output shape to the sibling tool modrinth_projects. An agent can immediately distinguish this from modrinth_search or modrinth_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 an explicit usage condition: 'for sampling or discovery when no search term applies', which implicitly steers the agent away from search-based tools. It stops short of naming the preferred alternative tool outright, so the exclusion is inferred rather than stated.

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