POKEKA — Pokémon Card Prices

Card context

get_card_context

Read-only

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.

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
`nicknames`	No
`risk_flags`	No
`context_note`	No
`hoarding_tier`	No
`has_risk_flags`	No
`context_coverage_note`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

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.5/5.0

Behavior5/5

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

Beyond the readOnly/openWorld/destructive annotations, the description adds a crucial behavioral caveat: 'Absence of flags is not a clearance; coverage is curated and growing.' It also discloses exact-match nickname behavior and lists the informational components returned, giving the agent important expectations beyond the schema.

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?

The description is compact: it front-loads the core content list, then explains the input options, and ends with an important safety caveat. Every sentence earns its place, with no redundant repetition of schema or annotations.

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?

The description covers what the tool returns, how to address a card (card_id or exact nickname), and the key caveat about coverage. An output schema is present, so return-value detail is not required. For a read-only contextual lookup tool, nothing essential is missing for an agent to select and invoke it correctly.

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 schema already covers both parameters with descriptions, so the baseline is 3. The description adds value by providing concrete example nicknames ('凡高皮', '金拱门') and explicitly emphasizing that the query must be an exact community nickname or alias, which is not fully stated in the schema descriptions.

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?

The description states a specific verb ('get'), a clear resource ('one card'), and enumerates specific content: nicknames, counterfeit-risk flags with self-check steps, holder-turnover tier, and a context note. It distinguishes itself from price-only siblings by explicitly saying 'beyond the price' and by naming card-level rather than market-level scope.

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?

The description clearly implies when to use this tool: when you need non-price context around a specific card. However, it does not explicitly mention alternatives or when not to use it, such as comparing this with slang_lookup for nickname resolution or card_price for price-only queries. The usage signal is present but left to inference.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?