Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cardmarket_catalog

Search Cardmarket product catalogues by name, category, or expansion; read public singles, non-singles, and accessory exports as paginated catalogue snapshots, not current seller offers.

Instructions

Search Cardmarket product catalogues. Reads the public singles, non-singles, or global accessories export and applies local name/category/expansion filters. Category and expansion IDs and labels are discovered from the complete selected file. Game IDs 26-33 have price guides but no verified catalogue files. The response is a catalogue snapshot, not current seller offers.

Input Schema

NameRequiredDescriptionDefault
qNoOptional case-insensitive local product-name substring, up to 200 characters
kindNoCatalogue file type; defaults to singles
limitNoRows per page, 1-500; defaults to 100
offsetNoZero-based offset; defaults to 0
game_idNoRequired for singles/nonsingles; omit for global accessories
category_idNoOptional current category ID; discover the full set with /cardmarket/catalog/categories
expansion_idNoOptional current expansion ID; discover the full set with /cardmarket/catalog/categories

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and discloses the public export source, local filtering, ID discovery from the selected file, and catalogue coverage gaps. It does not mention rate limits or authentication, but 'Reads the public ... export' clearly implies a safe read operation and the response nature is stated.

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?

Four sentences, front-loaded with the purpose and followed by concrete constraints; no filler. The dense sentence about category and expansion IDs being discovered from the complete selected file earns its place by explaining discovery behavior.

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

Completeness3/5

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

For a seven-parameter tool with no annotations and no output schema, the description covers data source, filtering, and coverage gaps but barely explains what a catalogue snapshot contains beyond 'not current seller offers.' It leaves the return structure and field semantics undocumented, which is a meaningful gap when no output schema exists.

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 coverage is 100%, so the schema already documents all seven parameters. The description adds some meaning by mapping the filters (name/category/expansion) and noting game ID limitations, but it does not elaborate on q, limit, or offset beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence states a specific verb and resource ('Search Cardmarket product catalogues') and distinguishes the output from seller offers and from price-guide-only game IDs. It does not explicitly name sibling tools like cardmarket_price_guide or cardmarket_catalog_categories, so sibling differentiation is indirect.

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?

It explains which export types are read, that local name/category/expansion filters apply, and gives a clear exclusion: game IDs 26-33 have price guides but no verified catalogue files. It also warns the response is a snapshot, not current seller offers, which helps route between catalogue and offer data, though it never names an alternative tool explicitly.

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