Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

boardgamegeek_taxonomy

Read-only

Return the pinned, dated BoardGameGeek website taxonomy: canonical object types, verified and unverified subtypes, per-object-type link types, hotness object types, thread sorts, geeklist categories/sorts, media licenses/galleries and the video/file language ids, with the verification date and provenance notes. Use it before calling boardgamegeek_entity, boardgamegeek_links or boardgamegeek_media so an enum value is never guessed; it takes no parameters and makes no upstream request. Re-verify the pinned values before changing them.

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

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.8/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses that the values are pinned and dated with provenance notes, that the call is local with no upstream request, and that stale values should be re-verified before being changed. That tells the agent both the cost profile and the trust/freshness characteristics of the returned data, which the annotations alone do not.

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 content inventory are front-loaded, then usage guidance, then the maintenance caveat, in a logical order with no filler. The enumeration of taxonomy sections makes the first sentence long, but each clause maps to real return content rather than padding.

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?

An output schema exists, so return-value structure need not be re-explained, and the description instead covers the things the schema cannot: when to call it, that it is parameterless and network-free, and how fresh/pinned the values are. For a zero-parameter reference tool this is complete.

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?

There are zero parameters, so the baseline is 4, and the description reinforces this by stating it "takes no parameters." There is nothing further to document on the input side.

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 ("Return the pinned, dated BoardGameGeek website taxonomy") and then enumerates exactly what the payload covers: object types, subtypes, link types, hotness types, thread sorts, geeklist categories/sorts, media licenses and language ids. It also names the three sibling tools it feeds (boardgamegeek_entity, boardgamegeek_links, boardgamegeek_media), so an agent can place it in the tool graph without ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is stated as an explicit precondition: call it before the entity, links and media tools so an enum value is never guessed. It also gives the operational boundary ("takes no parameters and makes no upstream request") and a maintenance rule ("Re-verify the pinned values before changing them"), leaving little to inference.

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