Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

speedrun_category_detail

Retrieve complete Speedrun category details by native category ID, including game and variable metadata, board records, ties, pagination, and variable source scopes.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
idYesNative category ID, opaque alphanumeric
embedNoNative metadata embeds, comma-separated

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

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 carries the full behavioral burden and does disclose several traits: native metadata wrappers, excluded account/profile embeds, tie preservation, empty boards, native pagination, and variable source scope. However, it does not clarify auth/rate-limit behavior or the exact response structure, and the records/variables sentences are confusing for a category-detail endpoint.

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?

The description is front-loaded with the core purpose and remains fairly compact. It is weakened by redundancy between the first two sentences and by later sentences about records and variable resources that do not clearly connect to this tool's two parameters.

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?

The tool is simple with only an id and embed parameter, and the description covers the ID constraint and some embed behavior. But because there is no output schema and no annotations, it should more clearly explain what category detail is returned and how this differs from the separate records and variables tools.

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 parameter descriptions already do most of the work. The description adds useful meaning by steering callers toward native discovery IDs rather than mutable abbreviations and by explaining how metadata embeds behave and what is excluded.

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 uses a specific verb and resource: 'Get Speedrun category detail,' and says it returns complete native category detail and context. The purpose is clear, but it does not explicitly differentiate this tool from sibling tools such as speedrun_category_records or speedrun_category_variables.

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 description gives a parameter-usage rule ('Use game/category/level discovery IDs, not mutable abbreviations') but does not say when to use this detail tool versus the related records or variables tools. There are no explicit exclusions or alternative-selection guidance.

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

Deploy Server

Other Tools