Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

speedrun_catalog

Retrieve Speedrun.com filter catalogs with native opaque IDs and pagination so you can filter platforms, regions, genres, engines, developers, and publishers accurately.

Instructions

Discover Speedrun.com filter catalogs. Reads anonymous Speedrun.com v1 metadata and preserves native opaque identifiers, run context and pagination. Source attribution: Speedrun.com.

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": {
      "kind": "<kind>"
    },
    "name": "speedrun_catalog"
  }
}

Input Schema

Name	Required	Description
`max`	No	Native page size from 1 to 200
`kind`	Yes	Native metadata collection
`offset`	No	Native zero-based result offset

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

B3.4/5.0

Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does meaningful work: it discloses that reads are anonymous (no auth), that they are read-only metadata against the v1 API, and that opaque native identifiers and pagination are preserved. It stops short of rate limits, response shape, or error behavior, but the safety and auth profile an agent needs is present.

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?

Three short sentences, front-loaded with the purpose before the operational caveats. The attribution sentence is arguably filler for an agent but is defensible as a source-credit requirement.

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 three-parameter read-only catalog tool with no output schema, the description should hint at what a catalog entry looks like (id plus display name) since nothing else covers the return value. It covers access, identifier preservation, and pagination, but leaves the response structure entirely unexplained.

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%, so kind, max, and offset are already fully documented in the schema. The description adds only indirect value by noting that native opaque identifiers and pagination semantics are preserved, hinting that offset/max are passthroughs to Speedrun.com rather than tool-invented, but adds no per-parameter detail.

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 ('Discover') and resource ('Speedrun.com filter catalogs') and the enum of kinds in the schema confirms these are metadata lookup collections. It distinguishes itself reasonably from record/leaderboard siblings by framing the resource as 'filter catalogs', though the phrase 'filter catalogs' is non-standard and the description never names the actual collections (platforms, genres, engines) the way the schema does.

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 explicit when-to-use guidance: nothing says to call this to resolve IDs before calling leaderboard or game tools, and no sibling is named or excluded. 'Discover ... catalogs' only implies the context, leaving the agent to infer the workflow from the tool name alone.

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

Deploy Server