Skip to main content
Glama

search_cards

Search Disney Lorcana cards using filters for color, cost, stats, keywords, and more. Get card objects with details for deck building and analysis.

Instructions

Search Lorcana cards with optional filters. Returns card objects (not counts). Color must be one of: ruby, sapphire, emerald, amber, amethyst, steel. Use card_type to filter by card type: Character, Action, Item, Song, or Location. Use min_attack/max_attack and min_defence/max_defence for stat-based queries (e.g. 'characters with 4+ strength'). Use min_cost/max_cost for cost ranges. Use keyword to filter by Lorcana keyword (Bodyguard, Challenger, Evasive, Reckless, Resist, Rush, Shift, Singer, Sing Together, Support, Vanish, Voiceless, Ward, etc.) — matches against the structured ability list, more reliable than substring search. Use body_text to search card ability text — useful for value-specific keyword queries like 'Singer 5' or 'Resist +2', or for non-keyword phrases like 'gain 2 lore'. Use lore/min_lore/max_lore to filter by lore value. Use sort_by to order results (id, name, cost, strength, willpower, lore, rarity, set_code); use sort_order='asc' or 'desc'. Use set_code to filter by set number (e.g. '1' for The First Chapter). Use set_name to filter by set name as a case-insensitive substring (e.g. 'Wilds Unknown', 'frozen', 'Floodborn') — preferred when the user names a set in plain English so you don't have to look up the code first. Use offset to paginate through results (e.g. offset=20 for the next page). Use count_cards instead if you only need a total count. Set response_format='toon' to receive a TOON-encoded string instead of JSON objects (~10% fewer tokens; the printings array is nested so the savings are smaller than a purely flat schema would yield); default is 'json'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
costNo
loreNo
nameNo
colorNo
limitNo
traitNo
offsetNo
rarityNo
inkwellNo
keywordNo
sort_byNoid
max_costNo
max_loreNo
min_costNo
min_loreNo
set_codeNo
set_nameNo
body_textNo
card_typeNo
max_attackNo
min_attackNo
sort_orderNoasc
max_defenceNo
min_defenceNo
response_formatNojson

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns card objects (not counts), explains the TOON encoding option for token savings, and implies read-only behavior through its search nature. However, it does not explicitly state that the operation is idempotent or free of side effects, which is acceptable given the context. The description is transparent enough for a search tool.

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?

The description is well-structured, starting with the core purpose and then systematically covering each parameter. It uses clear language and examples. While it is lengthy (necessary due to 25 parameters), it remains focused and every sentence contributes meaning. A slight deduction for verbosity at times, but overall efficiently organized.

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?

Given the complexity of 25 parameters and the presence of an output schema, the description covers all essential aspects: parameter usage, pagination, sorting, output format options, and alternative tools. It provides complete guidance for an agent to correctly invoke the tool, including edge cases like set_name vs set_code. The description is thorough and leaves no critical gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With schema description coverage at 0%, the description fully compensates by explaining the purpose and usage of most parameters in detail. It lists valid color values, explains keyword vs body_text differences, provides sort_by options, and clarifies set_name preference over set_code. Only a few parameters like 'trait' and 'name' are not explicitly described, but the coverage is extensive and adds significant value beyond the schema.

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 clearly states the tool's purpose: 'Search Lorcana cards with optional filters.' It explicitly mentions it returns card objects (not counts), distinguishing it from count_cards. The verb 'search' combined with 'Lorcana cards' and the mention of filters makes the purpose specific and unambiguous.

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?

The description provides extensive guidance on when to use this tool versus alternatives, such as 'Use count_cards instead if you only need a total count.' It explains when to use specific parameters for different query types (e.g., keyword vs body_text, set_name vs set_code) and how to paginate with offset. This gives clear context for usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/danielenricocahall/lorcana-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server