POKEKA — Pokémon Card Prices

Search cards

search_card

Read-only

Search graded Pokémon cards by name (Chinese / English / Japanese), community nickname (e.g. "鬼皮"), or set code + card number (e.g. "sv8a 喷火龙", "CEL 4"). 中文用户: 按官方卡名/圈内简称/系列码+卡号查任意宝可梦评级卡, 返回 card_id 供查价/走势/存世量工具使用。Returns up to 10 matching cards with card_id (incl. rarity/variant/species fields) — use card_id with the other tools. A bare set code or set name (e.g. "151c", "Celebrations") returns a set-level summary with guidance instead of a truncated card list — follow it to get_set_overview / set_species_summary for whole-set stats. Optional lang filters to one language track (en / ja / zh-cn); tracks are never mixed.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`lang`	No	Optional language track filter.
`query`	Yes	Card name, nickname/slang, or set code + number. zh/en/ja all accepted.

Output Schema

TableJSON Schema

Name	Required	Description
`hint`	No
`lang`	No
`query`	No
`sample`	No
`by_lang`	No
`results`	No
`guidance`	No
`mismatch`	No
`set_code`	No
`by_rarity`	No
`condition`	No	"raw" when the user asked for an ungraded card
`query_type`	No	"set" = the query was a bare set code/name; read guidance and use the set-level tools
`exact_match`	No	true only when set, number AND every other entity in the query (character, nickname, language) agree with the results
`total_cards`	No
`result_count`	No
`safe_to_price`	No	true = results[0] can be priced without asking the user to confirm; false = candidates only
`grading_filter`	No
`qualifier_note`	No
`unresolved_note`	No
`also_matched_sets`	No
`unresolved_tokens`	No
`qualifiers_dropped`	No

Schema Changelog

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

Changed7 schema fields changedSep 3, 2026

addedOutput schema / properties / condition

Added value: +{
+  "description": "\"raw\" when the user asked for an ungraded card",
+  "type": "string"
+}

changedOutput schema / properties / exact_match / description

Previous value: -"false = the set/number qualifier in the query was NOT satisfied by any result"New value: +"true only when set, number AND every other entity in the query (character, nickname, language) agree with the results"

addedOutput schema / properties / grading_filter

Added value: +{
+  "additionalProperties": true,
+  "properties": {
+    "company": {
+      "type": "string"
+    },
+    "grade": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / mismatch

Added value: +{
+  "additionalProperties": true,
+  "properties": {
+    "matched_character": {
+      "type": "string"
+    },
+    "matched_name": {
+      "type": "string"
+    },
+    "requested_terms": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / safe_to_price

Added value: +{
+  "description": "true = results[0] can be priced without asking the user to confirm; false = candidates only",
+  "type": "boolean"
+}

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

addedOutput schema / properties / unresolved_tokens

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed18 schema fields changedAug 27, 2026

addedOutput schema / properties / also_matched_sets

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / by_lang
```
Added value: +{
+  "type": "object"
+}
```

addedOutput schema / properties / by_rarity

Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "properties": {
+      "display_cjk": {
+        "type": "string"
+      },
+      "display_en": {
+        "type": "string"
+      },
+      "n": {
+        "type": "number"
+      },
+      "tier": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

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

addedOutput schema / properties / query_type

Added value: +{
+  "description": "\"set\" = the query was a bare set code/name; read guidance and use the set-level tools",
+  "type": "string"
+}

addedOutput schema / properties / results / items / properties / character

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

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

addedOutput schema / properties / results / items / properties / rarity

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

addedOutput schema / properties / results / items / 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 / results / items / properties / rarity_tier

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

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

addedOutput schema / properties / results / items / properties / variant

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

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

addedOutput schema / properties / sample

Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "properties": {
+      "card_id": {
+        "type": "string"
+      },
+      "card_number": {
+        "type": "string"
+      },
+      "card_url": {
+        "type": "string"
+      },
+      "character": {
+        "description": "featured Pokémon (EN species name)",
+        "type": "string"
+      },
+      "dex_no": {
+        "type": "number"
+      },
+      "finish_tiers": {
+        "type": "string"
+      },
+      "gen_code": {
+        "type": "string"
+      },
+      "image_url": {
+        "type": "string"
+      },
+      "lang": {
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      },
+      "rarity": {
+        "description": "bilingual rarity bucket label",
+        "type": "string"
+      },
+      "rarity_display": {
+        "additionalProperties": true,
+        "properties": {
+          "cjk": {
+            "description": "JP-style code (SR/RR/…)",
+            "type": "string"
+          },
+          "en": {
+            "description": "official EN star-system name",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "rarity_tier": {
+        "description": "machine rarity tier key (double_rare/ultra_rare/…)",
+        "type": "string"
+      },
+      "set_code": {
+        "type": "string"
+      },
+      "set_name": {
+        "type": "string"
+      },
+      "variant": {
+        "description": "variant slot (master_ball/poke_ball/…); absent for normal",
+        "type": "string"
+      },
+      "variant_kind": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / set_code
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / total_cards
```
Added value: +{
+  "type": "number"
+}
```

Changed3 schema fields changedJul 31, 2026

addedOutput schema / properties / exact_match

Added value: +{
+  "description": "false = the set/number qualifier in the query was NOT satisfied by any result",
+  "type": "boolean"
+}

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

addedOutput schema / properties / qualifiers_dropped

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

First observedJul 29, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already mark this as read-only and non-destructive; the description adds meaningful behavior beyond that: a 10-result cap, the set-level fallback with guidance, the requirement to use card_id with other tools, and the guarantee that language tracks are never mixed. 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 query types and examples and remains organized across output limits, set behavior, and language filtering. The Chinese sentence partly restates the English content, but it is short and serves the bilingual user base.

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?

Given the output schema and annotations, the description covers everything needed: accepted query formats, result count, key returned fields, how to chain card_id into other tools, the set-only edge case, and language track behavior. No critical calling context is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for both parameters, and the description still adds substantial value: concrete syntax examples ('sv8a 喷火龙', 'CEL 4'), bare set-code handling, and the semantics of the lang filter. This is well beyond what the schema alone provides.

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 uses a specific verb-resource pair ('Search graded Pokémon cards') and enumerates the three accepted query forms: name, nickname, and set code + number. It also distinguishes this tool from siblings by explaining that bare set queries produce a set-level summary rather than a card list.

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 clearly routes bare set queries to get_set_overview / set_species_summary and instructs users to pass returned card_id to other tools. It does not explicitly contrast search_card with sibling slang_lookup, but the guidance is otherwise clear and actionable.

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?