Skip to main content
Glama

kkjdaniel-bgg-mcp

by ai.smithery
OverviewDiscussionsAdmin

bgg-details

Get detailed information about board games on BoardGameGeek (BGG) including description, mechanics, categories, player count, playtime, complexity, and ratings. Use this tool to deep dive into games found via other tools (e.g. after getting collection results or search results that only return basic info). Use 'name' for a single game lookup by name, 'id' for a single game lookup by BGG ID, or 'ids' to fetch multiple games at once (up to 20). Only provide one of these parameters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoThe BoardGameGeek ID of a single board game.
idsNoArray of BoardGameGeek IDs for fetching multiple games (max 20).
nameNoThe name of the board game to look up.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • removedInput schema / properties / full_details
      Removed value: -{
-  "description": "Return the complete BGG API response instead of essential info. WARNING: This returns significantly more data and can overload AI context windows. ONLY set this to true if the user explicitly requests 'full details', 'complete data', or similar. Default behavior returns essential info which is sufficient for most use cases.",
-  "type": "boolean"
-}
    • changedInput schema / properties / id / description
      Previous value: -"The BoardGameGeek ID of the board game"New value: +"The BoardGameGeek ID of a single board game."
    • changedInput schema / properties / ids / description
      Previous value: -"Array of BoardGameGeek IDs to get details for multiple games at once (maximum 20 IDs per request)"New value: +"Array of BoardGameGeek IDs for fetching multiple games (max 20)."
    • addedInput schema / properties / ids / items
      Added value: +{
+  "type": "number"
+}
    • changedInput schema / properties / name / description
      Previous value: -"The name of the board game"New value: +"The name of the board game to look up."
  2. First observed

TDQS

A4.6/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. It discloses the mutual exclusivity constraint (crucial behavioral rule), the batch limit of 20 games, and enumerates return fields (description, mechanics, etc.) to compensate for the missing output schema. Minor gap on rate limits or authentication requirements.

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?

Four sentences with zero waste: (1) capability and return fields, (2) contextual usage vs siblings, (3) parameter selection guidance, (4) mutual exclusivity constraint. Information is front-loaded and logically sequenced from 'what' to 'when' to 'how.'

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 3-parameter lookup tool with 100% schema coverage and no output schema, the description adequately compensates by listing return fields and explaining the single-vs-batch lookup patterns. Would benefit from explicit mention of error handling or rate limiting to achieve a 5.

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?

While input schema has 100% description coverage (baseline 3), the description adds significant value by clarifying the mutual exclusivity rule ('Only provide one') and mapping usage patterns ('Use 'name' for a single game lookup... 'ids' to fetch multiple games'). This contextual guidance prevents invocation errors.

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 opens with a specific verb ('Get detailed information') and resource ('board games on BoardGameGeek'), listing specific data fields returned (mechanics, categories, ratings, etc.). It clearly distinguishes from siblings by positioning this as a 'deep dive' tool to use after 'search results that only return basic info.'

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 states when to use ('to deep dive into games found via other tools'), gives concrete examples ('after getting collection results or search results'), and mandates critical constraints ('Only provide one of these parameters'). It effectively maps the workflow across the tool family.

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

All kkjdaniel-bgg-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