Skip to main content
Glama

Look up a card price

lookup_card
Read-only

Look up a Pokémon TCG card by name and/or number. Understands "édition 1" / 1st edition, reverse, language (anglais/EN/JP), condition (played/excellent), slabs (PSA 10) and shadowless in q. Returns up to 5 matches. priceEur is the matching print+state; nmRawEur is always the NM print. 1st-edition never falls back to unlimited. Shadowless and missing slab comps return priceEur null with a note — do not substitute NM. Each hit has a url to its PokéItem page (picture, versions, full price curve). Never returns marketplace listings (eBay, Vinted, Cardmarket, etc.). Do not paginate — there is no offset.

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

Input Schema

NameRequiredDescriptionDefault
qYesName, number, set, plus optional version/language/condition/grader (e.g. Charizard 4/102 1st edition English PSA 10).
gameNoCatalog game slug. Default pokemon.
graderNoPSA | CGC | BGS | PCA | … when asking for a slab.
versionNoNORMAL (unlimited, default), FIRST_EDITION, REVERSE, REVERSE_POKEBALL, REVERSE_MASTERBALL, COSMOS_HOLO, HOLO. Also inferred from q.
languageNoBinder language: FR, EN, IT, DE, ES, JP. Also inferred from q. ED1 EN ≠ ED1 FR.
conditionNoNEAR_MINT (default) | EXCELLENT | GOOD | PLAYED | POOR | GRADED. Also inferred from q.
gradeLabelNoLabel tier above a plain 10: "black" (BGS / CCC Black Label) or "gold" (CGC / SGC Pristine 10, CCC Gold Label). Also inferred from q.
gradeValueNoSlab grade, e.g. 10 or 9.5.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the read-only annotations, the description explains important behavioral rules: priceEur reflects the matching print and state, nmRawEur is always NM, 1st edition never falls back to unlimited, and missing slab or shadowless comps return null rather than substituting NM. It also clarifies the return shape with up to 5 hits, a PokéItem URL per hit, and no marketplace listings.

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?

The description is dense but well structured, starting with the core action and then layering in query syntax, price semantics, fallback rules, return format, and exclusions. Every sentence carries operational information and there is no 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?

For an 8-parameter lookup tool with no output schema, the description covers the missing return-value context well: match count, price fields, null behavior, URL inclusion, and exclusion of marketplace listings. It also states the no-pagination constraint, leaving no major operational gap.

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?

With 100% schema coverage, the schema already documents all parameters, so the baseline is 3. The description adds useful semantic context by explaining that q accepts natural-language edition, language, condition, slab, and shadowless cues, and that 1st-edition lookup has a strict no-fallback rule.

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 states a specific verb and resource: looking up a Pokémon TCG card price by name and/or number. It also distinguishes scope by saying results are capped at 5 matches and never include marketplace listings such as eBay or Cardmarket.

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 clear usage guidance for the q field, including supported natural-language signals like edition, language, condition, slabs, and shadowless. It also explicitly rules out pagination and marketplace results, though it does not name sibling alternatives such as lookup_item or scan_card.

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.