Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

boardgamegeek_links

Read-only

List one page of typed links for a BoardGameGeek object and return the linked item ids and names for the requested link type. objecttype defaults to thing; objectid and linktype are required, and the valid link types differ per object type (see boardgamegeek_taxonomy). showcount is 1 to 50 (default 25) and pageid is 1 to 1000; the upstream total is reported when available. An unknown object id is a 404.

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

Input Schema

NameRequiredDescriptionDefault
pageidNoOptional page number, 1 to 1000; defaults to 1.
linktypeYesRequired link type for the selected object type; see boardgamegeek_taxonomy for the complete per-object-type value space.
objectidYesRequired positive object id whose links 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 them: pagination bounds (showcount 1-50 default 25, pageid 1-1000), that an upstream total is reported when available, and that an unknown object id yields a 404.

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?

The purpose and page scope are front-loaded, and the remaining sentences pack constraints without filler. It is a single dense paragraph rather than clearly separated purpose/parameters/errors, which slightly hurts scannability.

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, a full schema, and an output schema that handles return shape, the description supplies the remaining essentials: required inputs, pagination limits, cross-reference to the taxonomy tool, and the 404 failure mode. Only minor gaps remain, such as other error or rate-limit 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?

Schema description coverage is 100%, so defaults, ranges, and the taxonomy reference are already documented in the schema; the description largely restates them. The one added nuance is that valid link types differ per object type, but the schema's linktype description already implies this dependency. Baseline 3 applies when the schema does the heavy lifting.

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 concrete verb and resource ('List one page of typed links for a BoardGameGeek object') plus the returned content ('linked item ids and names for the requested link type'). An agent can distinguish this link-listing operation from entity/game/thread siblings 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?

Explicitly says objectid and linktype are required, that objecttype defaults to thing, and that valid link types vary per object type with a pointer to boardgamegeek_taxonomy for the value space. It gives no when-not-to-use case (e.g. preferring boardgamegeek_entity for full object details), so it falls short of a 5.

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