Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

speedrun_category_variables

Retrieve complete native category variables and context by game, category, or level discovery ID, preserving ties, pagination, and source scopes for accurate board data.

Instructions

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

Input Schema

Name	Required	Description
`id`	Yes	Native category 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

A3.7/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 does disclose substantive behavior: native metadata wrappers are preserved, account/profile embeds are excluded, and variable resources return every applicable value with its source scope. Some of the disclosure ('records count places and preserve ties, empty boards and native pagination') describes leaderboard behavior that reads as out of scope for a variables endpoint, slightly muddying the signal.

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 identifier scope and return contract are front-loaded in the opening two sentences, and each of the four sentences carries distinct information with no filler. Density is high and some phrasing is jargon-heavy ('native wrappers', 'source scope'), but nothing is redundant.

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?

With no output schema, the description must convey what comes back, and it does — variables, every applicable value, and source scope — while also covering embed exclusion behavior. It does not state read-only status or pagination specifics for this endpoint, so it is strong but not exhaustive for a four-parameter retrieval tool.

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 all four parameters, including both enums, are already documented in the schema, so the baseline applies. The description adds only one genuine clarification beyond the schema — that IDs must be native discovery IDs rather than mutable abbreviations — which is useful but marginal against an already-complete 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?

The first sentence names a specific verb and resource ('Get Speedrun category variables') and the second narrows the scope to 'complete native category variables and context', which lets an agent tell it apart from speedrun_level_variables and speedrun_variables by resource scope. It stops short of explicitly contrasting itself with those siblings by name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives a real usage constraint — 'Use game/category/level discovery IDs, not mutable abbreviations' — which tells the agent how to supply inputs correctly. However, it never states when to choose this over speedrun_variables or speedrun_level_variables; correct usage is implied by 'category' in the name rather than stated.

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

Deploy Server