Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

speedrun_games

Search Speedrun.com game metadata by name, genre, platform, and more, returning native identifiers, optional embeds, and paginated results.

Instructions

Search Speedrun.com games. Reads anonymous Speedrun.com v1 metadata and preserves native opaque identifiers, run context and pagination. Source attribution: Speedrun.com.

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": "speedrun_games"
  }
}

Input Schema

Name	Required	Description
`max`	No	Native page size1–200, or1–1000 with _bulk=true
`name`	No	Native game name search
`_bulk`	No	Native compact page mode, max up to1000; disables embeds
`embed`	No	Native metadata embeds
`genre`	No	Native genre ID from catalog
`engine`	No	Native engine ID from catalog
`offset`	No	Native zero-based result offset
`region`	No	Region ID from the regions catalog
`orderby`	No	Native game order; similarity requires name
`romhack`	No	Legacy inclusion: true only typed games, false only untyped; omission includes both
`gametype`	No	Game-type ID from the gametypes catalog
`platform`	No	Platform ID from the platforms catalog
`released`	No	Native release year, including0 for unknown
`developer`	No	Native developer ID from catalog
`direction`	No	Native order direction
`publisher`	No	Native publisher ID from catalog
`abbreviation`	No	Exact native abbreviation

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

B3.4/5.0

Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral burden. It usefully discloses anonymous reads of Speedrun.com v1 metadata and says opaque identifiers, run context, and pagination are preserved, but it omits rate limits, error behavior, return shape, and the practical effect of pagination or embeds.

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 are front-loaded with the purpose and contain no filler. The phrase 'native opaque identifiers, run context and pagination' is somewhat abstract but still compact and relevant.

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 17-parameter search endpoint with no output schema, the description gives only high-level context and does not explain the returned object shape or how pagination and embeds affect results. The fully documented schema mitigates this, but the definition is not complete enough for a 5.

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% across all 17 parameters, so the schema already defines max, name, _bulk, embed, filters, ordering, and direction. The description adds no parameter-specific syntax, defaults, constraints, or interactions, so the baseline 3 is appropriate.

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 opening sentence gives a clear verb ('Search') and resource ('Speedrun.com games'), so the tool's core function is immediately identifiable. It does not explicitly differentiate itself from sibling tools such as speedrun_game_detail or speedrun_catalog, which keeps it from a 5.

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?

It implies the tool is for searching games and notes anonymous read access, but never states when to choose it over game-detail or catalog tools, or when filters like embed and _bulk are appropriate. Selection guidance is therefore implied rather than explicit.

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

Deploy Server