Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

boardgamegeek_game

Fetch a BoardGameGeek game by numeric ID to retrieve names, player counts, play time, age, description, images, typed links, and merged community ratings and rank data.

Instructions

Get a BoardGameGeek game's detail, ratings and links. Returns one BoardGameGeek game by its numeric item id: primary and alternate names, player counts, play time, minimum age, description and wiki text, official website, images, and the typed link map (designers, artists, publishers, categories, mechanics, families, expansions, versions, honors). Community ratings, rank lines, poll answers, and ownership/play counters are merged in, and the item's field schema is included. Uses BoardGameGeek's anonymous website JSON API; no token or login is involved.

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

Input Schema

NameRequiredDescriptionDefault
idYesBoardGameGeek game (thing) id, positive integer; Catan is 13

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 well: it discloses that the call uses BoardGameGeek's anonymous website JSON API and requires no token or login, and it explains that community ratings, poll answers and counters are merged in and that the item's field schema is included. It does not cover rate limits or behavior on an invalid id, which keeps it short of a 5.

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?

Purpose is front-loaded in the first sentence, followed by a return-content inventory and then the auth note. The long parenthetical of linked entity types is dense but each item is informative; nothing is redundant filler.

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?

There is no output schema, so the description must describe the payload, and it does so thoroughly (names, counts, play time, age, descriptions, images, link map, ratings, ranks, polls, counters). Only error/invalid-id behavior is unaddressed, which is a minor gap for a one-parameter read tool.

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 already documented as a positive integer with 'Catan is 13' as an example. The description restates 'numeric item id' but adds no format or edge-case detail beyond the schema, so the baseline 3 applies.

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 opens with a specific verb and resource ('Get a BoardGameGeek game's detail, ratings and links') and pins the scope to one item by numeric id. It is not explicit about how it differs from the similarly named sibling boardgamegeek_entity, but an agent can still tell it retrieves a single game record.

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?

Usage is implied rather than stated: fetch this when you have a BGG game id and need full game detail. There is no when-not guidance and no mention of alternatives such as boardgamegeek_links or boardgamegeek_entity for other id spaces, so routing depends on inference from the sibling names.

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