Skip to main content
Glama

search_cards

Search for Hearthstone cards by name, text, class, mana cost, type, rarity, set, keyword, or race. Returns a summary list of matching cards.

Instructions

Search for Hearthstone cards by name, text, class, mana cost, type, rarity, set, or keyword. Use this when you need to find cards matching specific criteria. Returns a summary list — use get_card for full details on a specific card.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoFree-text search across card name and text (uses FTS5)
player_classNoFilter by class (e.g. MAGE, WARRIOR, NEUTRAL)
mana_costNoFilter by mana cost (combine with cost_op for range queries)
cost_opNoCost comparison operator: eq, lt, lte, gt, gte (default: eq)eq
typeNoFilter by card type: MINION, SPELL, WEAPON, HERO, LOCATION
rarityNoFilter by rarity: FREE, COMMON, RARE, EPIC, LEGENDARY
card_setNoFilter by set code (e.g. CORE, CLASSIC, LOE)
keywordNoFilter by keyword in keywords JSON (e.g. BATTLECRY, TAUNT, CHARGE)
raceNoFilter by minion race/tribe (e.g. BEAST, DRAGON, MURLOC)
collectible_onlyNoOnly return collectible cards (default: true)
limitNoMax results to return, 1-50 (default: 25)
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only mentions 'Returns a summary list,' implying read-only behavior and limited details, but does not explicitly state read-only, no side effects, or other behavioral traits like pagination or performance. This leaves significant gaps.

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 only two sentences, front-loading the purpose and tool distinction. Every word is necessary, with no extraneous content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 11 parameters and no output schema, the description is adequate for basic use but lacks details on how queries work (e.g., fuzzy search, boolean operators) or result behavior. It is sufficient but not rich.

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% (all 11 parameters have descriptions in the schema). The description adds no additional parameter semantics beyond listing criteria, so it scores the baseline of 3.

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 it 'Search for Hearthstone cards' and lists numerous filter criteria, specifying the verb and resource. It distinguishes itself from sibling tool 'get_card' by noting that search returns a summary list and get_card provides full details.

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?

The description advises to use this tool 'when you need to find cards matching specific criteria' and points to 'get_card' for full details, giving clear context. It does not explicitly state when not to use, but the guidance is sufficient.

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/gregario/hearthstone-oracle'

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