Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

boardgamegeek_game

Read-only

Get one BoardGameGeek board game by id and return its merged item record: name, year, player counts, play time, minimum age, description, designers, artists, publishers, categories, mechanics, families, images, ratings, ranks, polls, ownership and play counts. Use an id from boardgamegeek_hotness, boardgamegeek_links or boardgamegeek_recommendations, for example 13 for Catan. Unknown ids are a 404; polymorphic source fields are preserved as the source sends them. This is the highest-value surface; use boardgamegeek_entity for non-game object types.

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
idYesRequired positive BoardGameGeek item id from boardgamegeek_hotness or boardgamegeek_links, for example 13 for Catan.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds useful behavior beyond them: unknown ids are a 404 and polymorphic source fields are preserved as the source sends them. It does not cover authentication or rate limits, but with annotations and an output schema the remaining disclosure burden is lower.

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?

The definition is front-loaded with the core action and id sourcing, so the main guidance is easy to find. The long enumerated return-field list and the subjective 'highest-value surface' phrase add some bulk, but the paragraph remains readable and purposeful.

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 one-parameter read-only lookup with annotations and an output schema, the description covers the essential invocation context: what it returns, where ids come from, how unknown ids behave, and which sibling to use for non-game objects. Nothing critical for calling the tool correctly is missing.

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 100%, and the schema already documents the required positive id with the Catan example. The description repeats that example and adds boardgamegeek_recommendations as a source, but it does not add format or validation meaning beyond the schema, so the baseline 3 is appropriate.

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?

The description states a specific verb and resource: 'Get one BoardGameGeek board game by id' and return its merged item record. It also distinguishes the tool from boardgamegeek_entity, which is used for non-game object types, so an agent can tell the two apart without opening the schema.

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?

It explicitly says to use an id from boardgamegeek_hotness, boardgamegeek_links, or boardgamegeek_recommendations, gives the Catan example 13, and notes that unknown ids return a 404. It also names the alternative boardgamegeek_entity for non-game object types, covering when to use this tool versus a sibling.

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

All Crawlora MCP toolsInspect
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.

Resources