Skip to main content
Glama

Search the card catalog

search_cards
Read-onlyIdempotent

Find Pokémon TCG cards by name, set, or collector number and return product IDs, rarity, and USD market prices to support accurate listing drafts.

Instructions

Search the Pokémon TCG catalog (TCGplayer data) by card name, optionally narrowed by set name or code and collector number. Returns productId, set, number, rarity and USD market price per sub-type (Normal, Holofoil, Reverse Holofoil). If several products match, ask the seller for the set or number instead of guessing.

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": {
      "name": "<name>"
    },
    "name": "search_cards"
  }
}

Input Schema

NameRequiredDescriptionDefault
setNoSet name or code, e.g. '151' or 'MEW'
kindNoOnly single cards or only sealed products
nameYesCard or product name, e.g. 'Charizard ex'
limitNoMax results, default 8
numberNoCollector number, e.g. '199/165' or '199'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds useful return-shape detail (productId, set, number, rarity, per-sub-type USD market price) and an ambiguity-handling rule, but says nothing about result ordering, empty results, or the distinction between card and sealed results.

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?

Three tight sentences: purpose first, return fields second, ambiguity handling last. No filler, and the most decision-relevant information is front-loaded.

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 no output schema, the description does the job of listing the returned fields, and annotations cover the read-only profile. The only gaps are minor: the 'kind' (card vs sealed) filter and the 'limit' default of 8 appear only in the schema, and ordering/pagination behavior is unstated.

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% with examples for every parameter ('151'/'MEW', '199/165'), so the schema does the heavy lifting. The description restates set/number narrowing and the name parameter but adds no syntax or format detail beyond the schema, making the baseline 3 appropriate.

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?

States a specific verb and resource ('Search the Pokémon TCG catalog (TCGplayer data)'), plus the optional narrowing dimensions and the exact fields returned, so an agent can distinguish it from price-lookup or store-search siblings without opening the 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?

Gives clear usage context (search by card name, narrow by set name/code and collector number) and an explicit fallback rule for ambiguous matches: ask for set or number rather than guessing. It does not name an alternative sibling tool or state when-not to use it, so it stops short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.