Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

boardgamegeek_recommendations

Read-only

Get the community recommendations for one BoardGameGeek game and return each recommended item with its recommendation counts. id is a positive game id and showcount is 1 to 50; an id with no recommendations is a valid empty result (count 0 with an empty list), not an error. Use boardgamegeek_game to expand a recommended item.

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

Input Schema

NameRequiredDescriptionDefault
idYesRequired positive BoardGameGeek game id.
showcountNoOptional number of recommendations, 1 to 50; defaults to 25.

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.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely useful behavior beyond them: an id with no recommendations returns count 0 and an empty list rather than an error, which prevents an agent from treating a valid empty result as a failure.

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?

Front-loads the core action and return value, then covers constraints, the empty-result case, and the follow-up tool in a short passage with no filler. Every clause carries a distinct piece of information.

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?

With an output schema present, the description needn't explain return values, yet it still clarifies the empty-result semantics, which is the main ambiguity for this tool. Only ordering or pagination behavior of the recommendation list is left unaddressed, a minor gap for a two-parameter read tool.

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%, so the schema already documents id as a required positive game id and showcount as 1 to 50 defaulting to 25. The description restates the positivity and range constraints but adds no syntax, format, or edge-case meaning beyond what the schema provides; baseline 3 applies.

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?

States a specific verb and resource: 'Get the community recommendations for one BoardGameGeek game', and adds the return shape (each recommended item with its recommendation counts). This clearly separates it from boardgamegeek_game, which the description names as the tool for expanding an item.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear context (one game's community recommendations) and an explicit follow-up route: use boardgamegeek_game to expand a recommended item. It does not state when-not to use it, e.g. versus other discovery tools, but the context is clear enough to select it.

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