Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cardmarket_games

Discover Cardmarket download game IDs and check whether singles and non-singles catalogue files exist, returning observed public S3 price-guide IDs without guessing product names.

Instructions

Discover Cardmarket download game IDs. Returns the exact observed public S3 price-guide IDs and whether singles/non-singles catalogue files are present. Product display names are not inferred from numeric IDs when the download index cannot provide a confirmed mapping.

Input Schema

NameRequiredDescriptionDefault

No arguments

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 does add real context: it discloses that only 'exact observed public S3 price-guide IDs' are returned and that display names are NOT inferred when the mapping is unconfirmed — an honest data-fidelity caveat. It does not state read-only explicitly or note rate limits, but for a zero-parameter discovery call this is a meaningful disclosure.

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 tight sentences, front-loaded with the core purpose before the return details and the non-inference caveat. The final sentence is dense but earns its place by flagging a data limitation the agent would otherwise assume away.

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 no-parameter tool with no output schema and no annotations, the description adequately covers what comes back and the key caveat. The remaining gap is workflow context — how the returned game IDs feed into cardmarket_catalog or cardmarket_price_guide — which is not stated.

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?

The tool takes zero parameters (empty schema), so there are no argument semantics to explain. Baseline 4 applies; the description adds nothing needed on this axis.

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 description states a specific verb+resource: 'Discover Cardmarket download game IDs' and clarifies it returns observed public S3 price-guide IDs plus singles/non-singles catalogue presence. It is clear what the tool produces, though it never names its Cardmarket siblings (cardmarket_catalog, cardmarket_price_guide) to sharpen the boundary.

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

Usage Guidelines3/5

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

Usage is only implied by the word 'Discover' and the description of returned IDs — an agent can infer this is a discovery/bootstrap call. There is no explicit when-to-use vs. when-not, and no mention of the sibling catalogue/price-guide tools that would be the natural alternatives.

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