Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

speedrun_game_detail

Retrieve complete Speedrun game details by native game ID, including metadata embeds, categories, levels, variables, platforms, and record counts with ties and native pagination.

Instructions

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

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 unusually well: it discloses that metadata embeds keep native wrappers, that account/profile embeds are excluded, that empty boards and native pagination are preserved, and that variable resources return every applicable value with its source scope. It does not cover auth, rate limits, or error behavior, but the disclosed quirks are the kind of thing an agent could not guess.

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?

Front-loaded and free of filler, but the back half is a run of telegraphic fragments ("Records count places and preserve ties, empty boards and native pagination") where the subject is ambiguous and the clauses are hard to parse. It is compact at the cost of clarity.

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 two-parameter read tool with no output schema, the definition covers the identity rules, embed semantics, and result-shaping caveats (ties, empty boards, pagination) that matter most. What remains missing is routing guidance versus sibling tools, which is a moderate but real gap.

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 already 100%, so the baseline is 3; the description earns above baseline by adding meaning the schema lacks — the ID must be a native discovery ID rather than an abbreviation, and embed behavior (native wrappers preserved, account/profile excluded) constrains how embed results should be interpreted.

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 game detail") and adds scope via "complete native game detail and context." It is distinguishable from category/level/leaderboard siblings by the resource noun, but it never names an alternative to contrast against.

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 prerequisite-style rule — use discovery IDs rather than mutable abbreviations — which is genuine usage guidance. However, it says nothing about when to reach for this tool over speedrun_games (listing) or speedrun_category_detail, so an agent must infer the selection boundary.

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