Skip to main content
Glama

POKEKA — Pokémon Card Prices

Population report

card_pop
Read-only

Graded population for one card: PSA population by grade (total / 10 / 9 / 8), CCIC population (total / 10 / 9.5 / 9), PSA gem rate and scarcity tier when available. 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": {
      "card_id": "<card_id>"
    },
    "name": "card_pop"
  }
}

Input Schema

NameRequiredDescriptionDefault
card_idYesCard id from search_card / slang_lookup.

Output Schema

NameRequiredDescriptionDefault
psaNo
ccicNo
noteNo
card_idNo
gem_rateNo
gem_rate_bandNo
scarcity_tierNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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. The description adds relevant behavioral context: it reads only POKEKA market data, discloses server-side logging, and confirms it does not modify user data, which goes beyond the structured 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 the tool's purpose and the data it returns, followed by concise behavioral constraints. The second sentence is slightly ancillary but not 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?

For a simple read-only, one-parameter tool with an output schema and safety annotations, the description covers purpose, data source, and behavioral constraints adequately. It could be improved with usage guidance, but it is complete enough to invoke correctly.

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 the single parameter card_id is already documented in the schema with a reference to search_card / slang_lookup. The description adds no further parameter meaning, so the baseline of 3 applies.

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 precisely states the resource and the exact graded population metrics returned (PSA by grade, CCIC by grade, gem rate, scarcity tier). It does not explicitly name a sibling or contrast with card_price/card_price_history, so it falls short of a 5.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no alternatives, and no prerequisites. The sentence about reading POKEKA market data and logging is a constraint/behavior, not usage guidance.

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