Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

itchio_catalog

Retrieve native itch.io catalog classifications and public metadata by category without account keys, purchases, or creator admin access.

Instructions

Get a native itch.io classification index. Reads public itch.io catalog metadata without account keys, purchases or creator administration.

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

NameRequiredDescriptionDefault
classificationYesWebsite catalog context

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral context and does add meaningful pieces: public read, no authentication, no purchase or creator-admin scope. It stops short of describing what the index returns, whether it is static taxonomy or counts, or any rate/limit behavior for a network-backed read.

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?

Two short sentences, front-loaded with the action and resource, with the access scope second. Nothing is wasted, though "native" is a mildly vague qualifier that does little work.

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

Completeness3/5

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

For a one-parameter tool with full schema coverage and no output schema, the description is adequate but leaves the return value entirely unexplained, so an agent cannot predict whether it gets a flat list of categories, nested structure, or example URLs. That is the main gap for the intended planning use.

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 description coverage is 100% and the single parameter is a fully enumerated list, so the baseline is 3. The description only echoes the notion of classification and adds no meaning about how the chosen classification affects the returned index.

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?

States a specific verb and resource ("Get ... classification index") and scopes it to itch.io catalog metadata. The word "index" signals a taxonomy/listing tool rather than a project search, which distinguishes it from browse-style siblings, though no sibling is named explicitly.

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: the phrase "without account keys, purchases or creator administration" rules out transactional/admin scenarios, suggesting this is for enumerating catalog categories. There is no explicit when-to-use statement or named alternative such as itchio_browse or itchio_tags.

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