Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

speedrun_level_detail

Fetch complete native Speedrun level detail by discovery ID to get categories, variables, pagination, ties, and empty-board context without mutable abbreviations.

Instructions

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.6/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 behavioral burden and delivers substantive detail: embeds preserve native wrappers, account/profile embeds are excluded, records count places and preserve ties including empty boards, and native pagination is retained. It omits auth, rate limits, and error behavior, but the disclosed return semantics go well beyond a generic 'detail' claim.

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?

Front-loads the purpose in the first sentence, then packs return semantics into short declarative clauses with no filler. The later sentences are dense and somewhat jargon-heavy (e.g. 'Records count places and preserve ties, empty boards and native pagination'), which costs a little readability.

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 two-parameter read tool with no output schema, the description mostly covers what comes back, including embed wrapper behavior and records/pagination semantics. It leaves 'context' undefined and does not describe the top-level shape of the response, so it is adequate rather than complete.

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 both parameters are already documented, and the description's ID-type warning largely restates the schema's 'Native level ID, opaque alphanumeric'. The note that metadata embeds keep native wrappers and exclude account/profile adds some meaning to the embed parameter, lifting it slightly but not far above the baseline.

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 Speedrun level detail') and adds that it returns 'complete native level detail and context', which distinguishes it from narrower siblings like speedrun_level_categories or speedrun_level_records. It stops short of explicitly naming those siblings, so an agent must infer the routing from the generic catalog names.

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?

Gives one concrete usage rule -- use game/category/level discovery IDs rather than mutable abbreviations -- which is real guidance about input selection. However it never states when to prefer this tool over speedrun_level_categories, speedrun_level_records, or speedrun_level_variables, leaving the choice implicit in the word 'complete'.

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