Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

speedrun_variables

Retrieve native game variable definitions from Speedrun.com by game ID, preserving opaque identifiers, run context, and pagination for accurate metadata use.

Instructions

Get native game variable definitions. 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_variables"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

B3.2/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 a read-only, unauthenticated operation, and it discloses that opaque identifiers, run context, and pagination are carried through. It does not cover error behavior, rate limits, or what a missing/invalid ID yields.

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 and resource. The attribution clause is boilerplate but short and plausibly required; otherwise there is no wasted wording.

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 single-required-parameter read tool with full schema coverage and no output schema, the definition covers auth posture, identifier handling, and pagination. The main omission is return-shape detail, which is partly hinted at by 'preserves ... run context and pagination'.

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% with two enumerated parameters, so the schema already documents every input, including 'id' as a native opaque game ID. The description reinforces the opaque-ID and ordering semantics ('preserves native opaque identifiers') but adds no format or usage detail beyond the schema.

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?

States a specific verb and resource ('Get native game variable definitions') scoped to a game, which implicitly separates it from the category- and level-scoped siblings. It stops short of explicitly naming that scope distinction, so the reader must infer it from the word 'game'.

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 explicit when-to-use guidance and no mention of alternatives, despite near-identical siblings (speedrun_category_variables, speedrun_level_variables) whose only visible difference is scope. The agent gets no statement like 'use this for game-wide variables; use the category/level variants for scoped ones'.

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

Deploy Server