Skip to main content
Glama

POKEKA — Pokémon Card Prices

Market movers

market_movers
Read-only

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. 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": {
      "lang": "<lang>"
    },
    "name": "market_movers"
  }
}

Input Schema

NameRequiredDescriptionDefault
langYesMarket track: "en", "ja" or "zh-cn".
windowNoChange window: "7d", "30d" or "90d". Omit to use the default window published for that track.
directionNo"up" = cards rising, "down" = cards falling. Default "up".

Output Schema

NameRequiredDescriptionDefault
noteNo
marketNo
moversNo
reasonNopresent when the board is empty because this track does not publish this window (not because nothing moved) — read note
windowNo
directionNo
anchor_dateNoThe window anchors to this latest-sale date; present it.
mover_countNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / movers / items / properties / change_pct_30d
      Added value: +{
      +  "description": "this card's 30-day change on its card page (same grade); present on the 7-day board",
      +  "type": "number"
      +}
  2. Changed4 schema fields changed
    • changedOutput schema / properties / movers / items / properties / price_basis / description
      Previous value: -"\"reference\" = price_usd is a PriceCharting aggregate, NOT our verified sales — say so when quoting it."New value: +"\"reference\" = price_usd is NOT a robust verified-sales median (price_method names the kind) — say so when quoting it."
    • addedOutput schema / properties / movers / items / properties / price_grade
      Added value: +{
      +  "description": "present when price_usd is at a different grade than the grade of this row",
      +  "type": "string"
      +}
    • addedOutput schema / properties / movers / items / properties / price_method
      Added value: +{
      +  "description": "kind of reference: market_reference / limited_sales_reference / historical_reference",
      +  "type": "string"
      +}
    • addedOutput schema / properties / reason
      Added value: +{
      +  "description": "present when the board is empty because this track does not publish this window (not because nothing moved) — read note",
      +  "enum": [
      +    "track_window_not_published"
      +  ],
      +  "type": "string"
      +}
  3. Changed3 schema fields changed
    • 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."
  4. Changed1 schema field changed
    • 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"
      +}
  5. Changed2 schema fields changed
    • 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."
  6. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, yet the description still adds substantive behavior: a liquidity gate requiring at least 5 verified sales in both current and base windows, median consistency checks, change capped at ±40%, a 20-card cap, and a same-card/same-grade guarantee. It also discloses server-side request logging and that no user data is modified.

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 trigger sentence leads, followed by parameter semantics, then the liquidity-gate rationale; it is front-loaded and dense with information. It runs long and the privacy-logging clause is somewhat tangential, but nothing is redundant filler.

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?

With an output schema present, the description need not explain return shape, and it still names the row fields (price_now, price_base, n_cur, n_prev) that make results interpretable. For a read-only, three-parameter tool, nothing an agent needs to call it correctly is missing.

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 coverage is 100% with enums on all three parameters, so the baseline is 3, but the description adds real meaning: market tracks never mix across lang values, direction defaults to up, and omitting window falls back to a default window published per track. That is genuine semantic value beyond the enum labels.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb-and-resource framing: which Pokémon cards are rising or falling, what is hot, and the biggest moves for a week/month. It implicitly separates itself from volume-oriented siblings by centering on price change rather than sales volume, but it never names a sibling, so differentiation is inferential rather than 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?

It gives a clear trigger clause ("Use when the user asks which Pokémon cards are rising or falling, what is hot, or the biggest moves this week/month"), which is exactly the kind of usage context an agent needs. There is no when-not guidance and no named alternative such as market_volume_leaders for volume questions.

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