Skip to main content
Glama

kkjdaniel-bgg-mcp

by ai.smithery
OverviewDiscussionsAdmin

bgg-price

Get current prices for board games from multiple retailers using BGG IDs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYesComma-separated BGG IDs (e.g., '12,844,2096,13857')
currencyNoCurrency code (default: USD)
destinationNoDestination country (default: US)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / currency / description
      Previous value: -"Currency code: DKK, GBP, SEK, EUR, or USD (default: USD)"New value: +"Currency code (default: USD)"
    • addedInput schema / properties / currency / enum
      Added value: +[
+  "DKK",
+  "GBP",
+  "SEK",
+  "EUR",
+  "USD"
+]
    • changedInput schema / properties / destination / description
      Previous value: -"Destination country: DK, SE, GB, DE, or US (default: US)"New value: +"Destination country (default: US)"
    • addedInput schema / properties / destination / enum
      Added value: +[
+  "DK",
+  "SE",
+  "GB",
+  "DE",
+  "US"
+]
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. Adds 'current' (implies real-time data) and 'multiple retailers' (indicates aggregated sources), but lacks disclosure on error behavior (invalid IDs), rate limits, caching behavior, or authentication requirements. Safe but incomplete behavioral coverage.

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?

Single sentence with zero waste. Front-loaded with action verb, immediately identifies domain (board games), scope (current prices), sources (multiple retailers), and critical input constraint (BGG IDs). Every phrase earns its place.

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?

Appropriate for a 3-parameter retrieval tool with 100% schema coverage. Absence of output schema is acceptable given the intuitive return type (price data), though explicit mention of return structure (e.g., 'returns price data per retailer') would strengthen completeness. Adequate for tool complexity.

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%, establishing baseline 3. Description mentions 'BGG IDs' which aligns with the 'ids' parameter, but adds no additional semantic context for 'currency' or 'destination' beyond what the schema already documents. No clarification on why destination matters for pricing.

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?

Description provides specific verb ('Get'), clear resource ('current prices for board games'), data source ('multiple retailers'), and key input requirement ('using BGG IDs'). Clearly distinguishes from siblings like bgg-search, bgg-details, and bgg-collection by focusing exclusively on commercial pricing data.

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?

Implies prerequisite of having BGG IDs ('using BGG IDs'), suggesting users need IDs beforehand, but does not explicitly state when to use this vs. bgg-search (to find IDs) or clarify workflow. No explicit 'when-not-to-use' or alternative guidance provided.

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