Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

bgg_game_details

Read-onlyIdempotent

Retrieve full BoardGameGeek game details by BGG ID, including name, year, rating, player count, playtime, description, categories, and mechanics.

Instructions

Get full details for a board game by its BGG ID - name, year, rating, players, playtime, description, categories, and mechanics.

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": {
      "gameId": "<gameId>"
    },
    "name": "bgg_game_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameIdYesBoardGameGeek game ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety and repeatability are covered by structured data. The description adds the field scope of the payload, which is useful, but says nothing about behavior for an invalid/unknown ID (error vs empty) or data freshness from BGG.

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?

One sentence, front-loaded with the verb and key, and the field list doubles as useful payload scope. No filler or repetition of the tool name.

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 one-parameter read tool with full annotation coverage, the definition is largely sufficient, and listing the returned fields compensates for the absent output schema. The remaining gap is failure behavior on unknown IDs, which an agent would have to discover at runtime.

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?

The single gameId parameter is fully documented in the schema ('BoardGameGeek game ID'), and the description only restates that lookup is by BGG ID. With 100% schema coverage and zero enum/regex detail needed, the baseline of 3 applies; it could have noted the numeric-string format to prevent passing a game name.

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 ('Get full details for a board game') plus the identifying key ('by its BGG ID') and enumerates the returned fields. It is clearly distinguishable from bgg_search or bgg_game_reviews by being an ID-based detail lookup, though it never names those siblings 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?

The ID-based framing implies this is a follow-up call after finding a game via bgg_search, but the description never says so or states any prerequisites. There is no 'use X instead when...' guidance, so the agent must infer the lookup-by-known-ID workflow.

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