Crawlora MCP

itchio_catalog

Read-only

Get the native default first page of one itch.io classification index and return every visible project card: id, title, canonical URL, description, creator and creator URL, cover image, displayed price and genre. classification is one of games, tools, game-assets, comics, books, physical-games, soundtracks, game-mods, misc (the website's own URL slugs; native codes such as assets are mapped internally). Only public catalog metadata is returned: no account keys, purchases, downloads or creator administration, and this is always the native first index page with no sort or pagination invented.

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": {
      "classification": "<classification>"
    },
    "name": "itchio_catalog"
  }
}

Input Schema

Name	Required	Description	Default
`classification`	Yes	Required catalog context, one of: games, tools, game-assets, comics, books, physical-games, soundtracks, game-mods, misc. These are the website's own URL slugs; the service maps each to its measured native classification code (for example game-assets to assets), so do not send the native code. Returns the native default first page of that classification index.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 11, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries most of the load and does add real context: only public catalog metadata is exposed, no account keys or creator administration, and the result is always the native first page with no invented sorting or paging. It stops short of describing ordering of the returned cards or any rate/robustness behavior, keeping it below 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?

The paragraph is front-loaded with the core action and the return shape, then closes with scope limits, so a reader gets the essentials in the first clause. The nine-value classification list is duplicated verbatim from the schema and could be dropped, which is the only real waste.

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?

With one required parameter, full schema coverage, an output schema, and read-only annotations, the definition covers everything an agent needs to invoke it correctly. The field enumeration in the description is arguably redundant given the output schema, but nothing essential 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 parameter's schema text already lists the nine slugs and explains the internal native-code mapping, so the description's repetition of the same list adds no new meaning. Baseline 3 applies since the schema does the semantic work.

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 uses a specific verb ('Get') on a specific resource ('native default first page of one itch.io classification index') and enumerates the returned card fields. It implicitly separates itself from richer browse siblings by insisting there is 'no sort or pagination invented', but it never names an alternative tool, so the differentiation is inferred rather than stated.

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: an agent can infer this is the call for a plain classification index listing. There is no explicit when-to-use, when-not-to-use, or pointer to itchio_browse / itchio_browse_options for sorted or paginated results, and the negative statements are about data scope (no purchases, downloads) rather than about choosing between tools.

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

All Crawlora MCP tools Inspect

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.