Skip to main content
Glama
HowLongToBeat MCP

HowLongToBeat MCP

by pierro-bn

Search HowLongToBeat

hltb_search_games
Read-onlyIdempotent

Search games by title to get estimated main story, extras, and completionist times. No account or API key needed.

Instructions

Find games by title with estimated main story, extras and completion times. Returns only the first upstream page, not exhaustive results. No account or API key required.

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": {
      "query": "<query>"
    },
    "name": "hltb_search_games"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesGame title, preferably its official title.
detailNoUse detailed for description, platforms and image URL.compact

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare the safe read profile (readOnlyHint, idempotentHint, destructiveHint=false), so the bar is lowered. The description still adds genuinely useful behavior: results are capped at the first upstream page rather than exhaustive, and no account or API key is needed, which tells the agent the call is unauthenticated and may be incomplete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences: purpose, then the truncation caveat, then the auth note. The purpose is front-loaded and every sentence carries distinct information with no repetition of the title or schema.

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 read-only search tool with no output schema, the description covers what is returned (three time estimates), how much is returned (first page only), and access requirements. What remains unstated, such as response shape and whether pagination is possible, is minor for a search endpoint that returns a capped list.

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 67%: query and detail are documented in the schema, while limit is only constrained (1-20, default 5) with no prose. The description adds nothing about limit, detail, or result-count tradeoffs, so it neither compensates for the gap nor falls below the baseline for a mostly-documented 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?

States a specific verb and resource ('Find games by title') and adds what the results contain (main story, extras, completion times), which is more than a tautology. It implies the search-vs-fetch distinction against the sibling hltb_get_game by scoping itself to title lookup, but never names or contrasts with that sibling explicitly.

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?

'Find games by title' implies the lookup use case, and the note that it returns only the first upstream page sets a boundary on when to rely on it. However, it never states when to prefer hltb_get_game over this search or any prerequisites, leaving the routing decision to inference.

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