Skip to main content
Glama

bgg_top_games

Read-onlyIdempotent

Retrieve the BGG Hotness list to find currently discussed and active board games. Specify a limit up to 50 to control how many games are returned.

Instructions

Get the BGG Hotness list - the most discussed and active board games right now.

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of games to return (max 50, default 20)

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=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that the list reflects currently discussed/active games, but does not mention return format, ranking behavior, pagination, or any rate-limit/authorship details.

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?

The description is a single front-loaded sentence with no wasted words. It immediately states what the tool returns and the temporal scope.

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 read-only public list endpoint with one fully documented parameter and rich annotations, the description is mostly complete. The only minor gap is that without an output schema it does not describe the shape of the returned list beyond calling it a 'Hotness list'.

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 'limit' parameter is fully documented in the schema with max 50 and default 20. The description adds no additional parameter semantics, so the baseline score of 3 is appropriate because the schema already carries the parameter information.

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 states a specific verb and resource: 'Get the BGG Hotness list', and clarifies it as 'the most discussed and active board games right now'. This is clear, though it does not explicitly distinguish the hotness list from sibling tools such as bgg_search or bgg_game_details.

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 phrase 'right now' implies the tool is for current trending games rather than historical or search-based lookups, but there is no explicit guidance about when to use it instead of bgg_search or bgg_game_details. Usage is therefore implied but not fully specified.

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