POKEKA — Pokémon Card Prices

Card context

get_card_context

Everything around one card beyond the price: community nicknames (圈内叫法), counterfeit-risk flags with self-check steps, holder-turnover tier (locked vs high-churn), and a curated context note — plus the headline price. Accepts card_id or an exact nickname via query (e.g. "凡高皮", "金拱门"). Absence of flags is not a clearance; coverage is curated and growing. Calls record usage and query metadata within POKEKA.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	No	Alternative to card_id: an exact community nickname or alias.
`card_id`	No	Card id from search_card / slang_lookup.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`card`	No
`note`	No
`headline`	No
`last_sale`	No
`nicknames`	No
`reference`	No
`price_note`	No
`risk_flags`	No
`context_note`	No
`price_status`	No
`release_date`	No
`hoarding_tier`	No
`has_risk_flags`	No
`context_coverage_note`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 10, 2026

addedOutput schema / properties / reference

Added value: +{
+  "additionalProperties": true,
+  "properties": {
+    "as_of": {
+      "description": "snapshot date of a reference (non-sale) price — quote it as of this date, not as today",
+      "type": "string"
+    },
+    "company": {
+      "type": "string"
+    },
+    "confidence": {
+      "type": "string"
+    },
+    "estimate_max_date": {
+      "description": "Latest sale included in a historical estimate; not the newest source sale.",
+      "type": "string"
+    },
+    "estimate_min_date": {
+      "type": "string"
+    },
+    "finish": {
+      "type": "string"
+    },
+    "grade": {
+      "type": "string"
+    },
+    "last_sold": {
+      "type": "string"
+    },
+    "market": {
+      "description": "Which market this sale actually happened in (USD/CNY/JPY). The other two currency fields are convenience conversions at current FX rates, NOT prices observed in those markets. A USD-market sale quoted in CNY does not mean the card trades at that price in China.",
+      "type": "string"
+    },
+    "n_sales": {
+      "type": "number"
+    },
+    "price_cny": {
+      "type": "number"
+    },
+    "price_jpy": {
+      "type": "number"
+    },
+    "price_usd": {
+      "type": "number"
+    },
+    "sale_date": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed5 schema fields changedSep 10, 2026

addedOutput schema / properties / headline

Added value: +{
+  "additionalProperties": true,
+  "properties": {
+    "company": {
+      "type": "string"
+    },
+    "grade": {
+      "type": "string"
+    },
+    "n_sales": {
+      "type": "number"
+    },
+    "price_cny": {
+      "type": "number"
+    },
+    "price_jpy": {
+      "type": "number"
+    },
+    "price_usd": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / last_sale

Added value: +{
+  "additionalProperties": true,
+  "properties": {
+    "company": {
+      "type": "string"
+    },
+    "grade": {
+      "type": "string"
+    },
+    "n_sales": {
+      "type": "number"
+    },
+    "note": {
+      "description": "Always quote this caveat with the number — it is one sale, not a valuation.",
+      "type": "string"
+    },
+    "price_cny": {
+      "type": "number"
+    },
+    "price_jpy": {
+      "type": "number"
+    },
+    "price_usd": {
+      "type": "number"
+    },
+    "sale_date": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / price_note
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / price_status
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / release_date
```
Added value: +{
+  "type": "string"
+}
```

Changed10 schema fields changedAug 27, 2026

addedOutput schema / properties / card / properties / character

Added value: +{
+  "description": "featured Pokémon (EN species name)",
+  "type": "string"
+}

addedOutput schema / properties / card / properties / dex_no
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / card / properties / finish_tiers
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / card / properties / gen_code
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / card / properties / rarity

Added value: +{
+  "description": "bilingual rarity bucket label",
+  "type": "string"
+}

addedOutput schema / properties / card / properties / rarity_display

Added value: +{
+  "additionalProperties": true,
+  "properties": {
+    "cjk": {
+      "description": "JP-style code (SR/RR/…)",
+      "type": "string"
+    },
+    "en": {
+      "description": "official EN star-system name",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / card / properties / rarity_tier

Added value: +{
+  "description": "machine rarity tier key (double_rare/ultra_rare/…)",
+  "type": "string"
+}

addedOutput schema / properties / card / properties / set_name
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / card / properties / variant

Added value: +{
+  "description": "variant slot (master_ball/poke_ball/…); absent for normal",
+  "type": "string"
+}

addedOutput schema / properties / card / properties / variant_kind
```
Added value: +{
+  "type": "string"
+}
```

First observedJul 29, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations indicate readOnlyHint=false, implying possible side effects; the description transparently states that calls record usage and query metadata within POKEKA. It also discloses that absence of flags is not clearance and coverage is curated and growing, which adds important caveats beyond annotations. No contradiction with annotations.

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 description is front-loaded with the core output, then usage, then caveats. It is reasonably concise for the amount of information conveyed, though slightly lengthy. Every sentence serves a purpose, but it could be tightened slightly without losing clarity.

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?

Given the tool's complexity, the description covers the main purpose, input methods, and important caveats. An output schema exists, so return values are documented elsewhere. The description provides enough context for an agent to correctly select and invoke the tool.

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 already covers both parameters with descriptions (100% coverage). The description adds value by clarifying that either card_id or an exact nickname can be used, and gives concrete examples (凡高皮, 金拱门). This helps agents understand the input format better than schema alone.

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?

Clearly states what the tool returns: community nicknames, counterfeit-risk flags with self-check steps, holder-turnover tier, curated context note, and headline price. This distinguishes it from sibling tools like card_price and card_price_history, which focus on price alone. The verb 'get' plus the resource 'card context' is explicit.

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?

The description explains how to use it: accepts card_id or exact nickname via query, with examples. It implies the use case (need context beyond price) but does not explicitly mention when not to use it or name alternative tools. However, the instruction is clear enough for an agent to decide when to invoke it.

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

All POKEKA — Pokémon Card Prices 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?