Skip to main content
Glama

POKEKA — Pokémon Card Prices

Set overview & checklist

get_set_overview
Read-only

Whole-set statistics for one Pokémon TCG set: total cards, per-language-track counts, breakdown by rarity (with EN star-system + JP-style display names) and by variant (Master Ball / Poké Ball mirror slots etc.), top featured Pokémon, plus a paginated card checklist. 中文用户: 一次拿到整个系列的卡表统计(总卡数/每稀有度几张/每变体几张/出场宝可梦), 不用逐张搜。Use for questions like "how many cards / SR cards are in 151c". Accepts internal set_code, official abbreviation (CEL) or set name. Catalog data only — for the most valuable cards in a set use set_top_priced_cards; per-card prices via card_price. Reads POKEKA market data only; server-side request logging is disclosed in the privacy policy; does not modify user data.

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": {
      "set_code": "<set_code>"
    },
    "name": "get_set_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoOptional language track filter — same code can be different products per track.
pageNoChecklist page (0-based), 50 cards per page in card-number order for every tier. Pass the next page until an empty page comes back (whole-set sweeps are rate-guarded).
set_codeYesSet code, official abbreviation, or set name (e.g. "151c", "sv2a", "CEL", "Celebrations").

Output Schema

NameRequiredDescriptionDefault
langNo
noteNo
by_langNo
guidanceNo
set_codeNo
by_rarityNo
checklistNo
by_variantNo
top_speciesNo
total_cardsNo
price_noticeNoPresent when prices are withheld from the rows (no POKEKA account on this connection): follow it.
species_noteNo
checklist_pageNo
checklist_cappedNo
checklist_page_sizeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / checklist / items / properties / market_level
      Added value: +{
      +  "description": "best price evidence across all printings and grades: live / reference / sale_only",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedOutput schema / properties / price_notice
      Added value: +{
      +  "description": "Present when prices are withheld from the rows (no POKEKA account on this connection): follow it.",
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / page / description
      Previous value: -"Checklist page (0-based). Anonymous/free tier: 20 cards/page, first 2 pages; Pro: 50/page (whole-set sweeps are rate-guarded)."New value: +"Checklist page (0-based), 50 cards per page in card-number order for every tier. Pass the next page until an empty page comes back (whole-set sweeps are rate-guarded)."
  4. Changed1 schema field changed
    • changedInput schema / properties / page / description
      Previous value: -"Checklist page (0-based). Anonymous/free tier: 20 cards/page, first 2 pages; Pro: 100/page, unlimited."New value: +"Checklist page (0-based). Anonymous/free tier: 20 cards/page, first 2 pages; Pro: 50/page (whole-set sweeps are rate-guarded)."
  5. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the description does not need to re-prove safety — though it does restate "does not modify user data" redundantly. It adds genuinely new context beyond annotations: data provenance ("Reads POKEKA market data only"), scope (catalog data only), and a disclosure that server-side request logging exists. It stops short of describing result shape or how the two breakdowns are keyed, which the output schema presumably carries.

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 core capability is front-loaded in the opening clause and the sibling routing lands before any housekeeping. There is some padding: the full Chinese sentence repeats the statistics list already given in English, and the trailing privacy/logging disclosure is boilerplate appended to an otherwise tight definition.

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?

With an output schema present, return-value detail is rightly left out, and the description covers purpose, alternatives, data provenance and mutation-safety. For a 3-parameter read tool this is nearly sufficient; the only soft spot is that it does not clarify how the language-track filter interacts with the rarity/variant aggregates.

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 coverage is 100% and all three parameters carry their own descriptions, so the schema is doing the heavy lifting. The description's contribution mirrors rather than extends it: "Accepts internal set_code, official abbreviation (CEL) or set name" restates the set_code and page/lang documentation without adding format rules or edge cases. Baseline 3 is appropriate.

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?

"Whole-set statistics for one Pokémon TCG set" is followed by an enumerated payload: totals, per-language-track counts, rarity breakdown (EN star system + JP display names), variant breakdown (Master Ball / Poké Ball mirrors), top featured Pokémon, and a paginated checklist. The scope is unmistakably a set-level aggregate rather than per-card data, and it contrasts implicitly with the per-card siblings it later names.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names a concrete trigger question ("how many cards / SR cards are in 151c"), then states an explicit boundary: "Catalog data only — for the most valuable cards in a set use set_top_priced_cards; per-card prices via card_price." An agent is told both when to call this and which sibling to call instead for the adjacent intents.

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