Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

itchio_top_rated

Retrieve a native top-rated games page from the public itch.io catalog without account keys, purchases, or creator administration.

Instructions

Get a native top-rated games page. Reads public itch.io catalog metadata without account keys, purchases or creator administration.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "itchio_top_rated"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoNative one-based page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose the useful profile: read-only public catalog access, no authentication, no purchase or creator-admin side effects. It says nothing about the return format, how deep pagination goes, 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.

Conciseness4/5

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

Two short sentences, front-loaded with the action and followed by the access profile. No filler, though the second sentence is a list of negatives rather than information that helps select the tool.

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-optional-param read tool this is close to adequate, and the safety profile is covered. However, with no output schema and no annotations, the description should clarify what a 'native page' actually returns (HTML page vs. structured list) and whether paginated results are bounded.

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?

The single optional parameter is already fully documented in the schema ('Native one-based page'), so the schema does the heavy lifting. The description only echoes that a 'page' is what is returned, adding no syntax, bounds, or default beyond the structured field.

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 a native top-rated games page.' An agent can tell this is a ranked-listing fetch rather than a search or project-detail call, though it never names which sibling (e.g. itchio_browse, itchio_catalog) to prefer for related needs.

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 when-to-use or when-not-to-use guidance and no alternatives are named. The clause about no account keys, purchases or creator administration scopes what the tool is not for, but it is framed as a capability boundary rather than routing advice.

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