Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

boardgamegeek_cardsets

Lists a BoardGameGeek game's card sets with card types, dimensions, quantities, and expansion flags, helping answer card-size or sleeving questions.

Instructions

List a BoardGameGeek game's card sets. Returns the card sets recorded for a game, including the base or expansion flag, notes, prior card-set family links, and each set's card types with physical width/height, quantity and quantity notes. Useful for card-size or sleeving questions. A game with no card sets returns a valid empty list.

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_cardsets"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesBoardGameGeek game id, positive integer; Catan is 13

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose useful behavior: the returned fields (base/expansion flag, notes, family links, card types with dimensions and quantities) and that a game with no card sets returns a valid empty list rather than an error. It says nothing about authentication, rate limits, pagination, or error behavior for invalid ids, leaving real gaps for an unannotated tool.

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 purpose is front-loaded in the first sentence, followed by return details and the empty-list edge case. Every sentence carries information, though the enumeration of returned fields is slightly dense and could be tightened.

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 simple one-parameter read tool with no output schema, the description compensates by describing the return payload and the empty-result case, which is the main thing an agent would otherwise have to guess. Only error and rate-limit behavior is left unaddressed, a minor gap at this complexity level.

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 single id parameter is already documented with format and an example ('Catan is 13'). The description adds no further meaning about the id, so the schema does all the work and the baseline of 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 ('List a BoardGameGeek game's card sets'), which is concrete enough to distinguish it from generic siblings like boardgamegeek_game or boardgamegeek_entity. It does not explicitly name a sibling it overlaps with, so it stops short of full differentiation, but the resource is narrow and unambiguous.

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?

It offers one use case ('Useful for card-size or sleeving questions'), which implies when to reach for it. There is no guidance on when not to use it, no mention of prerequisites such as needing a game id first, and no explicit alternative tool for related data.

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