Skip to main content
Glama

Search cards

search_cards
Read-onlyIdempotent

Use this when the user names a trading card or sealed product and you need its TickerMint product_id (required by card_price and price_history) or its set id (group_id, required by set_prices). Returns up to 25 matches with name, set, collector number, the latest raw market price in USD and the page URL. Covers Pokemon, One Piece, Disney Lorcana, Riftbound, Yu-Gi-Oh, Gundam and Dragon Ball Super Fusion World only.

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

Input Schema

NameRequiredDescriptionDefault
gameNoLimit to one game (pokemon, one-piece, lorcana, riftbound, yugioh, gundam, fusion-world). Omit to search every game.
limitNoResults to return, 1 to 25.
queryYesCard or product name, optionally with set or collector number, e.g. 'charizard ex 199/165'.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / game / anyOf
      Previous value: -[
      -  {
      -    "enum": [
      -      "pokemon",
      -      "one-piece",
      -      "lorcana",
      -      "riftbound",
      -      "yugioh",
      -      "gundam"
      -    ],
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "pokemon",
      +      "one-piece",
      +      "lorcana",
      +      "riftbound",
      +      "yugioh",
      +      "gundam",
      +      "fusion-world"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / game / description
      Previous value: -"Limit to one game (pokemon, one-piece, lorcana, riftbound, yugioh, gundam). Omit to search every game."New value: +"Limit to one game (pokemon, one-piece, lorcana, riftbound, yugioh, gundam, fusion-world). Omit to search every game."
  2. Changed4 schema fields changed
    • changedInput schema / properties / game / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "pokemon",
      +      "one-piece",
      +      "lorcana",
      +      "riftbound",
      +      "yugioh",
      +      "gundam"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / game / description
      Added value: +"Limit to one game (pokemon, one-piece, lorcana, riftbound, yugioh, gundam). Omit to search every game."
    • addedInput schema / properties / limit / description
      Added value: +"Results to return, 1 to 25."
    • addedInput schema / properties / query / description
      Added value: +"Card or product name, optionally with set or collector number, e.g. 'charizard ex 199/165'."
  3. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds useful context beyond that: the result cap of 25, the per-row fields returned, the inclusion of a latest raw market price, and the explicit game coverage boundary. It stops short of saying what happens on zero matches or whether results are ranked, which is the remaining behavioral gap.

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?

Three sentences, front-loaded with the usage trigger, followed by return shape and coverage limits. Almost no waste, though the enumerated game list slightly duplicates the schema enum. It reads cleanly and puts the most decision-relevant information first.

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?

An output schema exists, so return values need not be spelled out, yet the description still gives enough to know what comes back. Coverage boundaries and the downstream id contract are stated. Only minor gaps remain: no explicit note on zero-result behavior and no differentiation from the similarly named `search` sibling.

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%, so all three parameters are already documented in the schema, including the game enum list and the 1–25 limit range. The description reinforces the 25 cap and the game universe but adds no syntax guidance for `query` beyond what the schema example provides. Baseline 3 is appropriate when the schema carries the parameter burden.

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 and frames the tool by its purpose (resolving a card or sealed product to a TickerMint product_id or group_id). It explicitly names the downstream siblings that consume those ids — card_price, price_history, set_prices — so an agent can place it in the workflow without guessing.

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 a clear triggering condition ("when the user names a trading card or sealed product") and explains why to call it: the ids it returns are required by pricing tools. It also bounds coverage to seven named games. The one gap is that it doesn't distinguish itself from the sibling tool named `search`, which an agent must choose between.

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