Skip to main content
Glama

POKEKA — Pokémon Card Prices

Set species summary

set_species_summary
Read-only

Per-Pokémon breakdown for one set: how many card faces each species has and how they split across variants (base / Master Ball / Poké Ball / …). 中文用户: 这个系列里每只宝可梦有几张卡、各是什么版本(普卡/大师球闪/精灵球闪)一表拿全。Answers "which Pokémon has the most versions in this set". Counts are catalog facts, NOT pull-rate probabilities. 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": "set_species_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoOptional language track filter.
set_codeYesSet code, official abbreviation, or set name.

Output Schema

NameRequiredDescriptionDefault
langNo
noteNo
speciesNo
guidanceNo
set_codeNo
total_cardsNo
coverage_noteNo
species_countNo
species_covered_cardsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, it adds that it reads POKEKA market data only, that server-side logging is disclosed in the privacy policy, and that it does not modify user data – useful operational context. It stops short of describing result format or pagination, but with output schema present that gap is minor.

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?

Front-loads the core purpose and then layers the example query, the probability caveat, and the data-source disclosure efficiently. The bilingual duplicate paragraph adds length but serves a documented user segment, so the density is justified rather than wasteful.

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 covering return values and annotations covering the safety profile, the description supplies the remaining essentials: what is counted, what it is not (probabilities), and the data source. It is complete enough to invoke correctly, missing only explicit sibling routing.

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 description coverage is 100% and both parameters (set_code, lang) are already documented in the schema, so the baseline of 3 applies. The description's variant vocabulary (base/Master Ball/Poké Ball) concerns output values, not parameter meaning, so it adds no parameter-level guidance.

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?

States a specific resource and metric: a per-Pokémon breakdown for one set, counting card faces per species and their variant split (base / Master Ball / Poké Ball). It also draws a conceptual contrast with pull-rate tools, though it never names a specific sibling like get_set_overview or card_pop, so the differentiation is implied 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?

Provides a concrete use case ('which Pokémon has the most versions in this set') and clarifies the data is catalog counts, not probabilities, steering the agent away from pull-rate tools. However, it offers no explicit 'when not to use' statement or named alternative, so the routing is contextual rather than directive.

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