Skip to main content
Glama

find_card

Use this for any question that names a card in free text, including nicknames like Moonbreon, 1st edition or Shadowless, or an English or Japanese set title. Example: q="Example Set Example Card" or a nickname such as Moonbreon. Results are ranked with match_score, exact_match, variant, and a needs_clarification hint when more than one printing fits. 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": "find_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoFree text, for example 'Example Set Example Card', 'Moonbreon', or an English or Japanese set title.
gameNoOptional game slug.
nameNoOptional structured card name, if not using q.
numberNoOptional collector number.
languageNoOptional language filter.
set_nameNoOptional set name, including JP/EN equivalents such as Ruler of the Black Flame.

Output Schema

NameRequiredDescriptionDefault
cardsNo
totalNo
truncatedNo
next_cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / q / description
      Previous value: -"Free text, for example 'Base Set Charizard 1st edition', 'Moonbreon', or 'Obsidian Flames Charizard ex'."New value: +"Free text, for example 'Example Set Example Card', 'Moonbreon', or an English or Japanese set title."
  2. Added

TDQS

A3.6/5.0
Behavior3/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 well on cost/limits: free, 60/minute, 1000/day per key, shared with other free catalog calls. It also discloses ranking signals (match_score, exact_match, variant) and the needs_clarification hint for ambiguous printings, but says nothing about no-match behavior or what match_score values mean.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The intent and quota details are front-loaded and useful, but the nickname example is stated twice ('nicknames like Moonbreon' and then again 'a nickname such as Moonbreon'), wasting a full sentence on a redundant illustration.

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?

For a 6-parameter tool with an output schema and no annotations, the description covers the trigger, ranking output signals, ambiguity handling, and rate limits. The remaining gap is guidance on interpreting needs_clarification/match_score and how the optional structured fields interact with q.

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 the baseline is 3, and the description mostly repeats what the q parameter already documents ('Moonbreon', EN/JP set titles). It adds nothing about the structured name/number/set_name/language fields or how they combine with q.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly conveys a free-text card lookup: 'Use this for any question that names a card in free text', with concrete inputs like nicknames, 1st edition/Shadowless variants, and EN/JP set titles. It doesn't explicitly name a sibling to contrast with (e.g., search_cards or get_card), so differentiation is inferable rather than stated.

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 a concrete trigger condition - any query naming a card in free text, including nicknames - which is a clear 'when to use'. It stops short of stating when NOT to use it or naming the structured alternative for known IDs/names, leaving that routing to inference.

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