Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

speedrun_level_records

Retrieve Speedrun level records using native IDs to get complete leaderboard data with metadata embeds, tie-aware places, pagination, and variable values.

Instructions

Get Speedrun level records. Returns complete native level records and context. Use game/category/level discovery IDs, not mutable abbreviations. Metadata embeds preserve their native wrappers; account/profile embeds are excluded. Records count places and preserve ties, empty boards and native pagination. Variable resources return every applicable value and its source scope.

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_level_records"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Native level ID, opaque alphanumeric
`max`	No	Native page size 1–200
`top`	No	Top places, not runs; API budget 1–200; native default 3
`embed`	No	Native metadata embeds, comma-separated
`offset`	No	Native offset, nonnegative
`skip_empty`	No	Omit empty boards when true; explicit false is retained

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A3.6/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 burden and discloses useful behavior: records count places and preserve ties, empty boards are addressed, pagination is native, metadata embeds keep native wrappers, and account/profile embeds are excluded. It does not cover error behavior or auth/rate-limit context, but it is materially more informative than the name alone.

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?

The definition is front-loaded with the core purpose and then layers behavioral details efficiently. It is dense but not bloated; each sentence contributes to return behavior, edge cases, or ID usage.

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

Completeness4/5

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

For a six-parameter read tool with no output schema and no annotations, the description covers return semantics, embed behavior, tie/place counting, empty boards, pagination, and variable resources. The main missing piece is selection guidance against sibling tools, which keeps it from being fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: it warns to use discovery IDs rather than mutable abbreviations, clarifies place-counting versus runs, explains embed wrapper preservation/exclusion, and describes variable-resource value/scope behavior. Some details still overlap with the schema, so it is not a 5.

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 states a specific verb and resource: 'Get Speedrun level records.' It adds what is returned, 'complete native level records and context,' but does not explicitly distinguish this from siblings such as speedrun_level_leaderboard or speedrun_level_detail.

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?

The only usage-like instruction is 'Use game/category/level discovery IDs, not mutable abbreviations,' which is really parameter guidance. There is no explicit statement of when to use this tool instead of related record or leaderboard tools.

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

Deploy Server