Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

boardgamegeek_taxonomy

Retrieve BoardGameGeek's pinned enum taxonomy to validate object type, subtype, and link type combinations before calling other BoardGameGeek routes.

Instructions

List BoardGameGeek's object-type, subtype and link-type enums. Returns the complete pinned taxonomy this family accepts: the canonical object types and entity types, the live-verified subtypes for each object type (with separately listed unverified subtypes), the verified link types for each object type, and the hotness, media, media-filter and entity enums. Values were verified with anonymous live requests on the date in verified_at and are constants, not live reads. Use it to validate objecttype/linktype combinations before calling the other BoardGameGeek routes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "boardgamegeek_taxonomy"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses that values are constants rather than live reads, that they were verified with anonymous live requests, and that verification provenance lives in verified_at. It also flags that unverified subtypes are listed separately, which is exactly the kind of caveat an agent needs to trust the output.

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 is front-loaded in the first sentence and the action guidance lands last. The middle sentence is a long enumeration that partly restates the opening list, costing some tightness, but every clause still conveys distinct content about what the payload contains.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, no-output-schema reference tool, the description fully covers what is returned, how fresh and trustworthy it is, and how to use it with siblings. Nothing needed to invoke or interpret it correctly is missing.

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?

Zero-parameter tool, so the baseline is 4. The description still adds meaning by naming the enum families an agent will find (object types, entity types, subtypes, link types, hotness, media, media-filter, entity), telling the caller what to look up rather than just saying 'taxonomy'.

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 ('List') and a precise resource ('BoardGameGeek's object-type, subtype and link-type enums'), then enumerates the exact contents returned. It is clearly separated from the data-fetching siblings by framing itself as the reference layer ('before calling the other BoardGameGeek routes').

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?

Gives explicit usage context: validate objecttype/linktype combinations before calling other BoardGameGeek routes. That is a clear when-to-use with a named relationship to the sibling routes. It does not state when-not to use it or which sibling to consult for concrete data, so it stops 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.

Deploy Server

Other Tools