Crawlora MCP

hltb_game

Read-only

Get one HowLongToBeat game's public catalog record and community play-time estimates by numeric game id: name, aliases, type (game or dlc), the base game id when the record is DLC, platform/developer/publisher/genre lists, regional release dates, age-rating values, aggregate completion and review counters, and the four play-style time aggregates (main, main_plus_extras, completionist, all_styles) in seconds with each style's sample count plus its upstream average, median, low and high. Pass an id from hltb_popular or an HLTB /game/{id} URL; unknown ids return 404. A play style with no community submissions reports seconds 0 and sample_count 0, and every time is a community estimate rather than a guarantee. Use hltb_popular first when you have no id; no images, review text, reviewer identity, lists, accounts or other user data are returned. The read runs on the qualified 2026-11-11 fresh-connection browser profile, so a transport failure is reported as an upstream 503 rather than an empty record.

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": "hltb_game"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Required HowLongToBeat game id as a positive integer string, for example 2127. Get one from hltb_popular or from a HowLongToBeat /game/{id} URL; an unknown id returns 404.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 11, 2026

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the readOnlyHint/openWorldHint annotations: it discloses 404 on unknown ids, 0/0 sentinel values for play styles with no submissions, that times are community estimates rather than guarantees, that no user data or images are returned, and that transport failures surface as an upstream 503 on a dated browser profile. The only gap is that it does not describe response shape or size, which the output schema partly covers.

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 purpose and id sourcing are front-loaded, but the middle is a long comma-spliced enumeration of returned fields that largely duplicates what the output schema already provides. Several sentences earn their place (404, zero-sample semantics, 503 transport behavior), but the field catalog is padding given a schema exists.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool, the definition covers input provenance, unknown-id behavior, sentinel values for missing community data, the estimate caveat, data exclusions, and error semantics. Combined with an existing output schema and readOnly annotations, an agent has everything needed to call it correctly.

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% and the single id parameter is fully documented in the schema, including the positive-integer-string format, the hltb_popular/URL sourcing, and the 404 case. The description restates the same sourcing and 404 facts rather than adding new meaning such as id ranges or URL-parsing behavior, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get one HowLongToBeat game's public catalog record and community play-time estimates by numeric game id') and then enumerates the record contents. It is clearly distinguishable from catalog-search siblings like hltb_popular because it is keyed on a single numeric id.

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

Usage Guidelines5/5

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

Explicitly routes the agent: 'Use hltb_popular first when you have no id', and it also accepts an HLTB /game/{id} URL as an alternate id source. The failure condition (unknown ids return 404) is stated, so nothing about selection or input acquisition is left to inference.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.