Skip to main content
Glama

search_cards

Use this for any question about which trading card printing in Pokémon (English and Japanese), Magic: The Gathering, Yu-Gi-Oh!, One Piece, and Riftbound matches a name, set, or collector number. Filters are applied before the cap; pass number for 4/102, H9, or TG06 and omit set_name unless the user named the set, because H9 matches a stored H09 and a name ending in (H9); the response includes total, truncated, next_cursor, language, rarity, release_date, and set_id. For nicknames or mixed free text such as "Moonbreon" or "Example Set Example Card", prefer find_card. Free, limited to 60 per minute and 1000 per key per UTC day, shared with the other free catalog calls.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_cards"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameNoOptional game slug.
nameNoCard name, for example Example Card. Sample: name=Example Card, number=001/100, set_name=Example Set. 4/102 also matches 004/102; that rule is about number shape, not a specific card.
limitNoPage size, default 20, max 50.
cursorNoOffset cursor from the previous next_cursor.
numberNoCollector number, for example 4/102, H9, or TG06. 4/102 matches 004/102. H9 matches H09/H32 and a name ending in (H9). 4 does not match 4/102.
languageNoOptional. en or ja. Omit to search both.
set_nameNoSet name only when the user named the set. Family match: Base Set also returns Base Set (Shadowless) and Base Set (1st Edition), but not Base Set 2.

Output Schema

NameRequiredDescriptionDefault
cardsNo
totalNo
truncatedNo
next_cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / name / description
      Previous value: -"Card name, for example Charizard. Example: name=Charizard, number=004/102, set_name=Base Set."New value: +"Card name, for example Example Card. Sample: name=Example Card, number=001/100, set_name=Example Set. 4/102 also matches 004/102; that rule is about number shape, not a specific card."
    • changedInput schema / properties / number / description
      Previous value: -"Collector number, for example 004/102. 4/102 also matches 004/102; 4 does not match 4/102."New value: +"Collector number, for example 4/102, H9, or TG06. 4/102 matches 004/102. H9 matches H09/H32 and a name ending in (H9). 4 does not match 4/102."
    • changedInput schema / properties / set_name / description
      Previous value: -"Set name. Family match: Base Set also returns Base Set (Shadowless) and Base Set (1st Edition), but not Base Set 2."New value: +"Set name only when the user named the set. Family match: Base Set also returns Base Set (Shadowless) and Base Set (1st Edition), but not Base Set 2."
  2. Changed9 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
      +  "description": "Offset cursor from the previous next_cursor.",
      +  "type": "string"
      +}
    • addedInput schema / properties / game
      Added value: +{
      +  "description": "Optional game slug.",
      +  "enum": [
      +    "pokemon",
      +    "mtg",
      +    "yugioh",
      +    "onepiece",
      +    "riftbound"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / language / description
      Previous value: -"Optional. en for English or ja for Japanese. Omit to search both."New value: +"Optional. en or ja. Omit to search both."
    • addedInput schema / properties / language / enum
      Added value: +[
      +  "en",
      +  "ja"
      +]
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Page size, default 20, max 50.",
      +  "maximum": 50,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • changedInput schema / properties / name / description
      Previous value: -"Card name, for example Charizard"New value: +"Card name, for example Charizard. Example: name=Charizard, number=004/102, set_name=Base Set."
    • changedInput schema / properties / number / description
      Previous value: -"Collector number, for example 004/102. 4/102 also matches."New value: +"Collector number, for example 004/102. 4/102 also matches 004/102; 4 does not match 4/102."
    • changedInput schema / properties / set_name / description
      Previous value: -"Set name, for example Base Set"New value: +"Set name. Family match: Base Set also returns Base Set (Shadowless) and Base Set (1st Edition), but not Base Set 2."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "cards": {
      +      "items": {
      +        "additionalProperties": true,
      +        "description": "Catalog card with id, name, name_native, number, set, game, language, rarity, and release_date.",
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "next_cursor": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "total": {
      +      "type": "integer"
      +    },
      +    "truncated": {
      +      "type": "boolean"
      +    }
      +  },
      +  "type": "object"
      +}
  3. Changed2 schema fields changed
    • addedInput schema / properties / language
      Added value: +{
      +  "description": "Optional. en for English or ja for Japanese. Omit to search both.",
      +  "type": "string"
      +}
    • changedInput schema / properties / number / description
      Previous value: -"Collector number, for example 4/102"New value: +"Collector number, for example 004/102. 4/102 also matches."
  4. First observed

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and delivers unusual specifics: cost ('Free'), hard quotas (60/min, 1000/key/UTC day, shared across free catalog calls), and the semantic that filters apply before the cap. It also names truncation and cursor fields, so an agent knows results may be incomplete. It stops short of stating result ordering or how an empty result set is signaled.

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-loaded with the routing statement, then constraints, then quota — a sensible order with no filler sentences. It is dense to the point of strain (one sentence carries three conditional rules) and repeats some number examples already present in the schema descriptions.

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 a 7-parameter, all-optional search tool with an output schema, the description covers the gaps that structured fields cannot: rate limits, quota sharing, pre-cap filtering, and truncation/cursor behavior. Return-field documentation is partly redundant with the output schema, but nothing an agent needs to call it 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%, so baseline is 3, but the description adds cross-parameter reasoning the schema cannot express: pass number for '4/102, H9, TG06' and omit set_name unless the user named the set, because H9 collides with a stored H09 and a name ending in (H9). That interaction guidance meaningfully changes how an agent composes arguments.

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... trading card printing') and enumerates the five supported games plus the three match keys (name, set, collector number). It explicitly contrasts itself with the sibling find_card for nicknames/free text, so an agent can route between them without 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 Guidelines5/5

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

Gives when-to-use ('any question about which printing ... matches a name, set, or collector number'), when to use the alternative ('For nicknames or mixed free text ... prefer find_card'), and a concrete calling rule ('omit set_name unless the user named the set'). Exclusions and alternatives are both present.

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