Skip to main content
Glama

boardgamegeek_threads

Read-only

Get List a BoardGameGeek object's forum threads. Returns one page of forum threads for a BoardGameGeek object (game, family, person, company, property or version), sorted by hot, recent or active. Each row carries the thread id, subject, forum, author, post/last-post dates, post count, pin/lock flags and hrefs, and the response includes the forums that object exposes with their thread/post counts so callers can discover the forumid filter. Use boardgamegeek_thread to read a thread's articles.

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

Input Schema

NameRequiredDescriptionDefault
sortNoOptional thread sort: hot, recent or active. Defaults to recent.
pageidNoOptional page number, 1 to 1000; defaults to 1.
forumidNoOptional forum id from this route's forums list to restrict the threads to one forum.
objectidYesRequired positive object id whose threads are listed.
showcountNoOptional page size, 1 to 100; 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.3/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 real behavioral context beyond them: results are a single page, sorting by hot/recent/active, and the response includes the object's forum list with thread/post counts. Auth or rate-limit behavior is not mentioned.

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?

Purpose and the sibling hand-off are front-loaded and the sentences are purposeful. The enumeration of row fields (id, subject, forum, author, dates, counts, flags, hrefs) is somewhat verbose given an output schema already exists, making it the one segment that does not fully earn its place.

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 annotations covering safety and an output schema covering return values, what remains for the description is scoping, sorting, and forum discovery — all present. It is complete enough to call correctly, with the only redundancy being the return-field list.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning: the forumid filter is discoverable from the forums list returned by this same route, and sort values are contextualized as hot/recent/active. It does not restate defaults, which the schema already carries.

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 ('List a BoardGameGeek object's forum threads'), scopes it to one page, and explicitly routes thread-content reading to the sibling boardgamegeek_thread. An agent can distinguish it from that sibling without opening either 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?

Names the alternative (boardgamegeek_thread) and the condition that selects it, and explains how to obtain a forumid to narrow results. It does not spell out when-not-to-use cases beyond that, so it falls short of full when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.