Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

speedrun_levels

Retrieve native game levels from Speedrun.com by game ID, with optional category and variable embeds, native ordering, and preserved opaque identifiers for accurate run context and pagination.

Instructions

Get native game levels. 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_levels"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Native opaque alphanumeric game ID
`embed`	No	Metadata embeds
`orderby`	No	Native level order
`direction`	No	Native order direction

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

C2.8/5.0

Behavior3/5

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

With no annotations, the description does real work: 'Reads anonymous ... v1 metadata' signals no authentication is required and that this is a read-only operation, and 'preserves ... pagination' discloses that results are paged. However, 'preserves native opaque identifiers, run context and pagination' is jargon that doesn't tell the agent what is actually returned or how paging is expressed, leaving gaps for a tool with zero annotation coverage.

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 action; the attribution line is a required source credit rather than filler. Slightly under-specified rather than verbose, but nothing is wasted.

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

Completeness2/5

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

A 4-parameter list tool with no annotations and no output schema needs the description to explain both the required game ID and the shape of returned levels/pagination; instead it offers a vague claim about preserving 'run context and pagination' without concrete detail. The structured fields carry most of the load, leaving the definition thin for its complexity.

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% and both enums are documented inline, so the baseline of 3 applies. The description adds essentially nothing about `id`, `embed`, `orderby` or `direction` beyond the vague phrase 'preserves native opaque identifiers', which only loosely gestures at the ID parameter.

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 game levels" names a verb and resource, but "native levels" is ambiguous – it never says these are the levels belonging to a game identified by the required `id`, and it does nothing to separate this list operation from siblings like speedrun_level_detail, speedrun_level_categories or speedrun_level_leaderboard. An agent can guess it lists levels, but must open the schema to confirm the game-scoped relationship.

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 statement of when to call this versus the many sibling level tools (detail, categories, leaderboard, records, variables). The only hints are indirect: 'preserves ... pagination' implies a collection endpoint, but no explicit alternative is named or excluded.

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

Deploy Server