Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

boardgamegeek_links

Lists typed BoardGameGeek links for games, families, people, companies, properties, and versions, letting you retrieve related mechanics, categories, designers, publishers, expansions, or credits.

Instructions

List a BoardGameGeek object's typed links. Returns one page of a typed link list for an object: for a game, its mechanics, categories, designers, publishers, expansions or versions; for a family, its games; for a person, their credits; for a company, its games; for a property, its games; for a version, its parent game and publishers. Each row carries the linked object's identity, name, post date, subtype and image. The link type must be valid for the requested object type; see boardgamegeek-taxonomy for the complete per-type value space.

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": {
      "objecttype": "<objecttype>",
      "objectid": "<objectid>",
      "linktype": "<linktype>"
    },
    "name": "boardgamegeek_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageidNoPage number, 1-1000
linktypeYesLink type; must be one of the values verified for the object type (see boardgamegeek-taxonomy)
objectidYesObject identifier, positive integer; Catan is 13
showcountNoPage size, 1-50
objecttypeYesCanonical object type that owns the links

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the burden and does reasonably well: it discloses that results are paginated ('Returns one page') and enumerates the row shape (identity, name, post date, subtype, image), which compensates for the absent output schema. It does not mention rate limits, auth, or what happens with an invalid linktype/objecttype pairing beyond the constraint statement.

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?

Front-loaded with the verb+resource, then the per-type examples which are dense but genuinely informative. The enumeration is long but each clause maps a distinct object type to useful link values, so it mostly earns its space.

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 5 params, 3 required, 100% schema coverage and no output schema, the description covers purpose, valid link scope, pagination, and return-row fields. Only minor gaps remain: failure behavior for mismatched objecttype/linktype pairs and how to traverse past the first page.

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 real meaning by linking linktype semantics to objecttype ('for a game, its mechanics, categories, designers...for a version, its parent game and publishers'), clarifying the interaction between two required parameters. It does not clarify pageid bounds or showcount behavior beyond the schema.

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 typed links') and immediately narrows scope to what links mean per object type (game -> mechanics/designers, family -> games, person -> credits). An agent can tell this is a link-relation enumerator rather than a general entity lookup like boardgamegeek_entity.

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?

The per-object-type enumeration gives clear selection context: if you need a game's designers or a family's member games, this is the tool. It also points to boardgamegeek-taxonomy to validate link types. It stops short of explicitly naming when to prefer a sibling tool or stating exclusions.

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