Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

speedrun_records

Fetch native top-one game record boards from Speedrun.com by game ID, preserving opaque identifiers, run context, and pagination for leaderboard lookups.

Instructions

Get native top-one game record boards. 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": {
      "id": "<id>"
    },
    "name": "speedrun_records"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Native opaque alphanumeric game ID
`max`	No	Native page size from 1 to 200
`top`	No	Top places, API budget1–200; compatibility default1
`embed`	No	Metadata embeds
`offset`	No	Native zero-based result offset
`skip_empty`	No	Omit empty boards when true; explicit false preserved

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

C2.9/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; it does disclose useful behavior: anonymous unauthenticated reads, Speedrun.com v1 as the source, preservation of native opaque identifiers, run context and pagination. It omits error behavior, rate limits, and what a board actually contains, so the disclosure is partial rather than rich.

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 tight sentences with the core purpose front-loaded and no filler. The trailing source-attribution sentence is mandated boilerplate rather than agent-helpful content, which keeps it just below a top score.

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 six-parameter, no-annotation, no-output-schema tool, the description covers access model and identifier handling but leaves the shape of returned boards and pagination semantics unexplained. Adequate to attempt a call, but not complete enough to predict results.

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 every parameter is already documented, and the description adds little beyond echoing that the id is a native opaque identifier. The baseline of 3 applies because the schema does the heavy lifting here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Get native top-one game record boards" gives a verb and resource and implies game-scoped boards, but "top-one" and "record boards" are ambiguous and the definition never differentiates itself from the near-identical sibling speedrun_game_leaderboard. An agent can guess it fetches top records for a game, but not precisely how it differs from other leaderboard tools.

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 named alternative, even though several siblings (speedrun_game_leaderboard, speedrun_category_records, speedrun_level_records) cover adjacent territory. The only usage-adjacent fact is that access is anonymous.

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

Deploy Server