Skip to main content
Glama

tcgdata.dev — European TCG Prices

See a card image

get_card_image
Read-only

Return verified WebP artwork as an MCP image block, with request metadata. Use the ID and query fields from images.small/large; catv_ source variants require their parent catalogue_card_id. Never pass an arbitrary image URL. One admitted API call consumes one shared account request, including admitted errors. No automatic retries.

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": {
      "card_id": "<card_id>"
    },
    "name": "get_card_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNolarge
card_idYesReturned tcg_, cat_ or catv_ ID from an authenticated catalogue response.
catalogue_card_idNoRequired parent cat_ ID for a catv_ image; omit for other IDs.

Output Schema

NameRequiredDescriptionDefault
okYes
apiYes
requestYes
http_statusYes
next_actionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / face
      Removed value: -{
      -  "description": "Zero-based Magic face index, only with tcg_ IDs; copy from the returned image path.",
      -  "maximum": 9,
      -  "minimum": 0,
      -  "type": "integer"
      -}
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations it discloses quota accounting ('One admitted API call consumes one shared account request, including admitted errors') and failure semantics ('No automatic retries'), which explains why an otherwise read-only fetch is flagged non-idempotent. It also specifies the returned artifact type and that request metadata accompanies it. This is substantive context the structured fields cannot convey.

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?

The output contract is front-loaded, followed by input provenance, a prohibition, and cost semantics — each sentence carries distinct information. It is dense with sub-clauses, though no sentence is filler.

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?

With three parameters, a partial schema-coverage score, and an output schema already defining return values, the remaining burden is provenance, cost, and retry behavior — all addressed. An agent can call this correctly without consulting other tools.

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?

Schema coverage is 67%, so the description must compensate for gaps and does: it tells the agent the IDs come from images.small/large in a prior response, ties catv_ usage to catalogue_card_id, and forbids raw URLs (reinforcing the card_id pattern). The size parameter's effect is only implied through the 'images.small/large' reference rather than explained directly.

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 pairs a specific verb and resource ('Return verified WebP artwork as an MCP image block') with the payload shape, so an agent knows it yields image bytes rather than card metadata. It is clearly distinct from fetching a card record, though it never names a sibling tool to sharpen that contrast.

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 states the prerequisite ('Use the ID and query fields from images.small/large'), the conditional case ('catv_ source variants require their parent catalogue_card_id'), and an explicit prohibition ('Never pass an arbitrary image URL'). What is missing is an explicit statement of when to prefer this over the metadata siblings, but the input-provenance guidance is strong.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources