Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

boardgamegeek_geeklists

Read-only

Get List geeklists that link a BoardGameGeek object. Returns one page of the community geeklists that link an object, filtered by category (all, trade, general) and sorted by hot or recent. Each row carries the list title, author, item count, recommendation count and dates. The response includes the category filters the source offers and the list totals. Use boardgamegeek_geeklist and boardgamegeek_geeklist_items to read a list's content.

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": {
      "objectid": "<objectid>"
    },
    "name": "boardgamegeek_geeklists"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoOptional sort: hot or recent. Defaults to hot.
pageidNoOptional page number, 1 to 1000; defaults to 1.
categoryNoOptional category filter: all, trade or general. Defaults to general.
objectidYesRequired positive object id whose geeklists are listed.
showcountNoOptional page size, 1 to 50; defaults to 25.
objecttypeNoOptional object type: thing, family, person, company, property or version. 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.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real behavioral context beyond that: results are a single page, rows carry title/author/item count/recommendation count/dates, and the payload also echoes the available category filters and totals, which tells the agent how to interpret and continue paginating.

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?

Three sentences, front-loaded with the scope and page semantics, followed by the row/response shape and then sibling routing. No filler sentences, though the opening 'Get List geeklists that link...' is slightly awkward and repeats the resource name before the useful detail arrives.

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, return values needn't be enumerated, yet the description still summarizes the row fields so the agent knows what to expect. Six parameters with one required is handled adequately; the only minor gap is no mention of the page-number/page-size bounds, which the schema already covers.

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 every parameter including defaults (sort hot, category general, page 1) is already documented structurally. The description restates the category and sort options ('all, trade, general', 'hot or recent') but adds no syntax, constraints, or interaction detail beyond the schema, matching the baseline for high-coverage schemas.

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 names a specific verb and resource ('Get List geeklists that link a BoardGameGeek object') and immediately scopes it: one page, category-filtered, hot/recent sorted. It explicitly distinguishes itself from boardgamegeek_geeklist and boardgamegeek_geeklist_items, which read list content rather than listing lists.

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 explicit routing guidance: 'Use boardgamegeek_geeklist and boardgamegeek_geeklist_items to read a list's content,' which tells the agent when a different tool is appropriate. It does not state exclusions in the other direction (e.g., when this listing tool is a poor choice), so it stops short of a full when/when-not treatment.

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