Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

speedrun_level_variables

Retrieve complete Speedrun level variable data and context using native game, category, and level IDs; returns applicable values and source scopes.

Instructions

Get Speedrun level variables. Returns complete native level variables 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_variables"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Native level ID, opaque alphanumeric
`embed`	No	Native metadata embeds, comma-separated
`orderby`	No	Native contextual 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 carries the full disclosure burden, and it does add real detail: metadata embeds keep their native wrappers, account/profile embeds are excluded, and variable resources return every applicable value with its source scope. Against that, the sentences about records counting places, preserved ties, empty boards and native pagination appear to be boilerplate carried over from a leaderboard tool and misdescribe what this endpoint returns. No annotation to contradict, but the mixed messaging reduces trust in the behavioral claims.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Five short sentences that are readable and reasonably front-loaded with the purpose. However, the final three sentences cover records, ties, empty boards and pagination — material an agent calling a variables endpoint cannot act on — so they read as template filler rather than earning their place.

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 four-parameter read tool with no output schema, the description is only partly sufficient: it signals that variables plus context are returned and that every applicable value and source scope come back, which helps. It leaves the sort/direction parameters unexplained and substitutes leaderboard semantics for a description of the variable payload shape, so an agent would still need to probe the response.

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 coverage is 100%, so the schema already defines all four parameters including the two enums, which sets the baseline at 3. The description does add genuine meaning for id (native discovery IDs, not mutable abbreviations) and for embed (native wrappers preserved, account/profile embeds excluded), but orderby and direction are never addressed. Net addition is partial rather than compensatory.

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?

The opening sentence states a specific verb and resource ("Get Speedrun level variables"), which is clear enough on its own. However, the description then drifts into claims about records counting places, tied results, empty boards and pagination, which describe leaderboard/record behavior rather than variables, and it never distinguishes itself from the sibling tools speedrun_variables or speedrun_category_variables. The reader is left unsure whether this is a variables endpoint or a records endpoint.

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?

"Use game/category/level discovery IDs, not mutable abbreviations" is identifier guidance for the id parameter, not guidance about when to call this tool. Nothing states when to prefer it over speedrun_variables, speedrun_category_variables or speedrun_level_detail, and there are no exclusions or prerequisites.

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

Deploy Server