Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

boardgamegeek_hotness

Read-only

Get one BoardGameGeek hotness list and return the ranked hot items for the requested object type. objecttype is thing, person or company (defaults to thing) and showcount is 1 to 50; the list is a current-popularity snapshot, not an all-time ranking, and a brand-new showcount can briefly return an empty cached page. Use boardgamegeek_game to expand a hot item's detail.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "boardgamegeek_hotness"
  }
}

Input Schema

NameRequiredDescriptionDefault
showcountNoOptional number of entries, 1 to 50; defaults to 50.
objecttypeNoOptional hotness object type: thing, person or company. Defaults to thing.

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=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely non-obvious behavior: the result is a current-popularity snapshot rather than an all-time ranking, and a newly chosen showcount can briefly return an empty cached page — a quirk an agent would otherwise misread as an error.

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?

Two compact sentences, front-loaded with the action and ending with the alternative-tool pointer; no filler. The second sentence is slightly overloaded with parenthetical defaults, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need no explanation, and annotations cover read-only/open-world semantics. The description still supplies the scope, parameter bounds, the snapshot-vs-ranking caveat, the cache edge case, and the next-step tool — everything an agent needs to call this correctly.

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 both parameters and their ranges/defaults are already documented. The description restates the objecttype values and the 1–50 showcount bound without adding format or interaction details (e.g. whether showcount interacts with caching per value), so it stays at the baseline.

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?

The description opens with a specific verb and resource ("Get one BoardGameGeek hotness list and return the ranked hot items") and scopes it by object type, so an agent can distinguish it from entity/thread/game lookups without opening the schema.

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?

It gives an explicit hand-off ("Use boardgamegeek_game to expand a hot item's detail"), which routes follow-up detail lookups to the right sibling, and it frames the list as a popularity snapshot. It doesn't state when not to use this tool (e.g. historical/all-time rankings), but the guidance is clear.

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