Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

boardgamegeek_geeklist

Get a BoardGameGeek geeklist's detailed metadata and body, including title, creator, dates, flags, and sort order, for community list review.

Instructions

Get a BoardGameGeek geeklist's detail. Returns one community geeklist's metadata and body: title, creator id, post/edit dates, plain-text body, rendered bodyXml, privacy/comment/trade flags, sort direction and domain, and the source's discoverability links (items, comments, thumbs, tips). Use boardgamegeek_geeklist_items to page its entries.

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

Input Schema

NameRequiredDescriptionDefault
idYesBoardGameGeek geeklist id, positive integer

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It signals a read-only retrieval and discloses the returned fields, including privacy flags, but says nothing about access restrictions on private lists, error behavior for invalid ids, or rate limits.

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 sentences, front-loaded with the action and then the return payload, with the sibling routing at the end. The long comma-separated field enumeration is dense but earns its place since no output schema exists to carry that 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 no output schema, the description compensates well by naming the returned metadata fields, so an agent knows what to expect from the response. Given the tool's simplicity and the fully documented single parameter, the only real gap is the absence of any note on private-list access behavior.

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?

There is a single parameter with 100% schema description coverage ('BoardGameGeek geeklist id, positive integer'), so the schema already fully documents it. The description adds no format, range, or example detail beyond that, making the baseline 3 appropriate.

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 a BoardGameGeek geeklist's detail') and immediately enumerates what comes back (title, creator id, dates, body, bodyXml, flags, sort/domain, links). That level of specificity clearly separates it from the sibling plural 'boardgamegeek_geeklists' and from 'boardgamegeek_geeklist_items'.

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 routes the agent explicitly for the follow-on task: 'Use boardgamegeek_geeklist_items to page its entries,' which tells the agent this tool does not paginate entries. It does not explicitly contrast with boardgamegeek_geeklists (the listing tool), leaving that distinction to be inferred from the singular/detail wording.

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