POKEKA — Pokémon Card Prices

Market movers

market_movers

Use when the user asks which Pokémon cards are rising or falling, what is hot, or the biggest moves this week/month. lang = "en" / "ja" / "zh-cn" (market tracks never mix). direction = "up" (cards rising) or "down" (cards falling), default "up". window = "7d" / "30d" / "90d"; omit to use the default window published for that track. Every row passes a liquidity gate — at least 5 verified sales in both the current and the base window, change capped at ±40%, both medians consistent with the card's reference price — and carries price_now / price_base / n_cur / n_prev, so a listed move is a real same-card, same-grade move. Up to 20 cards. Calls record usage and query metadata within POKEKA.

Input Schema

TableJSON Schema

Name	Required	Description
`lang`	Yes	Market track: "en", "ja" or "zh-cn".
`window`	No	Change window: "7d", "30d" or "90d". Omit to use the default window published for that track.
`direction`	No	"up" = cards rising, "down" = cards falling. Default "up".

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No
`market`	No
`movers`	No
`window`	No
`direction`	No
`anchor_date`	No	The window anchors to this latest-sale date; present it.
`mover_count`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 3, 2026

changedInput schema / properties / direction / description

Previous value: -"Gainers (up) or losers (down), default up."New value: +"\"up\" = cards rising, \"down\" = cards falling. Default \"up\"."

changedInput schema / properties / lang / description

Previous value: -"Market track."New value: +"Market track: \"en\", \"ja\" or \"zh-cn\"."

changedInput schema / properties / window / description

Previous value: -"Change window. Omit to use the default window published for that track."New value: +"Change window: \"7d\", \"30d\" or \"90d\". Omit to use the default window published for that track."

Changed1 schema field changedAug 28, 2026

addedOutput schema / properties / movers / items / properties / price_basis

Added value: +{
+  "description": "\"reference\" = price_usd is a PriceCharting aggregate, NOT our verified sales — say so when quoting it.",
+  "enum": [
+    "verified_sales",
+    "reference"
+  ],
+  "type": "string"
+}

Changed2 schema fields changedAug 1, 2026

changedInput schema / properties / lang / enum

Previous value: -[
-  "en",
-  "ja"
-]New value: +[
+  "en",
+  "ja",
+  "zh-cn"
+]

changedInput schema / properties / window / description

Previous value: -"Change window, default 30d."New value: +"Change window. Omit to use the default window published for that track."

First observedJul 29, 2026

TDQS

A4.8/5.0

Behavior5/5

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

The description goes well beyond the annotations (all false) by disclosing that calls record usage metadata, explaining the liquidity gate (minimum 5 sales, ±40% cap, median consistency), and describing the output fields (price_now, price_base, n_cur, n_prev). It also clarifies that market tracks never mix. This is rich, honest behavioral disclosure.

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 dense but well-organized: it leads with the usage trigger, then parameter explanations, then data quality and output details, and finally the side effect. Every sentence carries useful information; no filler. It earns its length.

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 tool's complexity and the presence of an output schema, the description covers everything an agent needs: usage trigger, parameter semantics, data filtering rules, output field names, row limit, and side effects. Nothing essential 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?

Although schema coverage is 100%, the description adds significant meaning: it explains what 'lang' implies (tracks never mix), the default for 'direction' and 'window', and the data-quality implications of the gate. It enriches the parameters beyond the schema's enum lists and 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 clearly states the tool's purpose: to show which Pokémon cards are rising or falling, what is hot, or the biggest moves. It specifies a concrete resource (market movers) and differentiates from volume or pricing tools by focusing on change. While it doesn't name a sibling, the context is unmistakable.

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 provides explicit when-to-use guidance: 'Use when the user asks which Pokémon cards are rising or falling, what is hot, or the biggest moves this week/month.' It also explains parameter selection (lang, direction, window) in detail. However, it doesn't mention when not to use it or point to alternatives, so it stops short of the top score.

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?