Scryfall MCP demonstrates solid fundamentals: all 4 tools have clear action-verb names (search_, get_, random_, list_), descriptions between 100-200 chars (within baseline 194 avg), and complete JSON Schema with required fields marked. Input schemas are well-formed with type declarations and enums (e.g., unique: ['cards','prints','art']). However, output schemas are NOT documented, callers cannot see what fields search_cards or get_card return without reading implementation. Error handling returns structured {error, message} but lacks recovery guidance (e.g., 'Try a simpler query'). Parameter descriptions are adequate but lack format hints (e.g., 'Scryfall query syntax' could specify 'Use operators like c:, type:, o:, set:, rarity:'). No tool annotations (readOnlyHint, idempotentHint) despite all being read-only. Results are capped at 40 items (good), but no pagination parameters (offset/limit) offered.
Look up a single Magic: The Gathering (MTG) card by name (fuzzy matching). Returns full card details including mana cost, oracle text, colors, prices, legalities, and image.
List all Magic: The Gathering (MTG) sets/expansions with codes, names, types, release dates, and card counts.
Get a random Magic: The Gathering (MTG) card, optionally filtered by a Scryfall query (e.g. "is:commander", "c:blue").
Search Magic: The Gathering (MTG) cards using Scryfall's powerful query syntax (e.g. "c:red type:dragon", "set:neo rarity:mythic", "o:flying cmc<=3"). Returns matching MTG cards with names, types, oracle text, sets, rarities, and prices.
Output schemas not documented. Callers cannot see what fields search_cards, get_card, random_card, or list_sets return without reading source code. LLMs cannot plan downstream operations or extract required fields.
No tool annotations (readOnlyHint, idempotentHint, destructiveHint). All 4 tools are read-only and idempotent, but this is not declared in the schema. Agents cannot distinguish safe tools from destructive ones.
Error responses lack recovery guidance. When Scryfall returns 404 or 400, the tool returns {error, message} but does not suggest next steps (e.g., 'Try search_cards() with a simpler query' or 'Check set code format').
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 63 | 2026-07-28+ | v2 |
search_cards lacks pagination parameters. Results are capped at 40 items, but no offset/limit/page parameters allow agents to fetch more. Large result sets cannot be fully explored.
Parameter descriptions lack format hints. 'Scryfall search query' does not explain syntax (c:red, type:dragon, o:flying, cmc<=3). Agents must infer valid operators from examples, risking malformed queries.