Crawlora MCP

cardmarket_catalog

Read-only

Returns a paginated Cardmarket daily product catalogue for singles, non-singles or global accessories. Provide game_id for singles/non-singles and omit it for accessories. The response discovers current category and expansion IDs; q and filters are applied locally.

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": {
      "Kind": "<Kind>",
      "GameID": "<GameID>",
      "CategoryID": "<CategoryID>",
      "ExpansionID": "<ExpansionID>",
      "Query": "<Query>",
      "Limit": "<Limit>",
      "Offset": "<Offset>"
    },
    "name": "cardmarket_catalog"
  }
}

Input Schema

Name	Required	Description
`Kind`	Yes	Catalogue file type; defaults to singles. Documented values: singles, nonsingles, accessories.
`Limit`	Yes	Rows per page, 1-500; defaults to 100
`Query`	Yes	Optional case-insensitive local product-name substring, up to 200 characters
`GameID`	Yes	Required for singles/nonsingles; omit for global accessories. Documented values: 1, 2, 3, 5, 6, 7, 8, 9, 10, 11, 12, 13, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25.
`Offset`	Yes	Zero-based offset; defaults to 0
`CategoryID`	Yes	Optional current category ID; discover the full set with /cardmarket/catalog/categories
`ExpansionID`	Yes	Optional current expansion ID; discover the full set with /cardmarket/catalog/categories

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

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 genuine context beyond that: filtering happens locally rather than server-side, and the response surfaces current category/expansion IDs — non-obvious behavioral traits for an agent.

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?

Three sentences, front-loaded with the core purpose and immediately followed by the mode/ID rule. No filler, though the density of clauses (game_id rule, local filtering, ID discovery) makes it slightly compressed.

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?

For a paginated catalogue tool with a full output schema and rich parameter docs, the description covers the essential modes, required IDs, and local-filtering behavior. Only the explicit pointer to the categories sibling for ID discovery is missing.

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% and each parameter is already documented, including the local-substring nature of Query and the game_id requirement. The description largely restates the GameID rule rather than adding new semantics, so baseline 3 applies.

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 ('Returns a paginated Cardmarket daily product catalogue') and enumerates the three modes (singles, non-singles, accessories). This differentiates it cleanly from siblings like cardmarket_games, cardmarket_price_guide, and cardmarket_catalog_categories.

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 concrete calling guidance: supply game_id for singles/non-singles, omit it for accessories, and notes that q and filters are applied locally. It also hints at the discovery path for category/expansion IDs, but does not explicitly name cardmarket_catalog_categories as the alternative to call.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

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

Need Help?