Skip to main content
Glama

get_population

Use this for any question about how many copies PSA has graded, or how scarce a PSA grade is. Population is PSA only, for cards in Pokémon (English and Japanese), Magic: The Gathering, Yu-Gi-Oh!, One Piece, and Riftbound. A card with no stored population is still a successful paid lookup, and a missing card id is not charged. $0.01 per success, limited to 120 per minute.

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": "get_population"
  }
}

Input Schema

NameRequiredDescriptionDefault
card_idYesCatalog card UUID

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / card_id / format
      Added value: +"uuid"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses that a card with no stored population still counts as a successful paid lookup, that a missing card id is not charged, the exact cost ($0.01 per success), and the rate limit (120/minute). These are exactly the behavioral traits — billing, edge-case success semantics, throttling — an agent needs before calling.

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?

Four sentences, front-loaded with the use case, then scope, then billing edge cases, then cost/rate limit. Every sentence contributes new information and nothing is repeated from the schema or annotations.

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?

An output schema exists, so return values need not be explained, and the description covers the remaining gaps: data source, coverage of games, cost, rate limit, and the no-population/missing-id edge cases. Nothing an agent needs in order to decide and call 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% for the single required card_id (UUID), so the schema already does the heavy lifting. The description adds a small but useful semantic point: an absent card id is not charged, which clarifies the consequence of the required-parameter constraint.

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 opens with a concrete use case ('any question about how many copies PSA has graded, or how scarce a PSA grade is') and then pins the exact resource scope: PSA population data only, across five named TCGs. That is specific enough to separate this tool from catalog or pricing siblings without the agent opening a schema.

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 an explicit when-to-use trigger ('any question about how many copies PSA has graded') plus a hard domain restriction (PSA-only, five named games). It stops short of naming an alternative or a when-not-to-use condition, so it is strong context rather than full routing 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