Skip to main content
Glama
Sign In

CARDZ MCP

by io.github.cardzgame
OverviewDiscussionsAdmin

Card metrics & history

get_card
Read-onlyIdempotent

Use this when the user wants detailed metrics for a specific card: PSA 10 reference price, population, market cap, price changes, daily history, and canonical URL. Requires an exact card ID from search_cards. Prices are daily published observations in USD, not live or executable quotes. Null values mean data is unavailable for that field — do not substitute zero.

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": {
      "id": "<id>"
    },
    "name": "get_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesExact CARDZ card ID returned by search_cards, e.g. cmc_fc229f7ae1b256b2119fa79b. Do not guess or construct IDs; always obtain from search_cards first.
langNoLanguage for display labels in the response. Does not filter by card language; use tcg to narrow by game. Printing language is always returned in the result.
historyDaysNoDays of price history to include, counting back from the most recent published point. Default 90; max 365. Omit for standard 90-day view.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / historyDays / description
      Previous value: -"Calendar days ending at the latest published history point; default 90."New value: +"Days of price history to include, counting back from the most recent published point. Default 90; max 365. Omit for standard 90-day view."
    • changedInput schema / properties / id / description
      Previous value: -"Exact public card ID from search_cards."New value: +"Exact CARDZ card ID returned by search_cards, e.g. cmc_fc229f7ae1b256b2119fa79b. Do not guess or construct IDs; always obtain from search_cards first."
    • changedInput schema / properties / lang / description
      Previous value: -"Display language; printing language is returned separately."New value: +"Language for display labels in the response. Does not filter by card language; use tcg to narrow by game. Printing language is always returned in the result."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior, so the bar is lower; the description still adds real value by clarifying that prices are daily published observations in USD rather than live/executable quotes, and that nulls mean unavailable and must not be treated as zero. It omits any mention of rate limits or data latency beyond the daily cadence.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three front-loaded sentences with zero filler: trigger and payload first, source-of-ID constraint second, data-semantics caveat last. Every clause earns its place.

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 no output schema, the description carries the return-value burden and does so by listing the metric fields and the canonical URL plus null-handling semantics. For a single-required-parameter read tool with rich annotations, nothing an agent needs to invoke or interpret it correctly 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 description coverage is 100%, so id, lang, and historyDays are already fully documented in the schema. The description only echoes the requirement that the ID come from search_cards and says nothing additional about lang or historyDays, so the baseline of 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 action and resource ('detailed metrics for a specific card') and enumerates exactly what is returned: PSA 10 reference price, population, market cap, price changes, daily history, canonical URL. This is clearly separable from search_cards (ID lookup) and get_market (broader market data).

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?

Opens with an explicit trigger ('Use this when the user wants detailed metrics for a specific card') and names the prerequisite dependency on search_cards for the ID. It does not state when to prefer get_market instead, so it falls short of full alternative routing.

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

All CARDZ 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