Loading ToolBench
Magic: The Gathering Commander format assistant providing card search, deck validation, legality checking, pricing, rulings, and deck recommendations from Scryfall, Moxfield, Archidekt, and EDHREC APIs
MTG Commander MCP Server has 19 well-named read-only tools with consistent verb_noun patterns (search_, get_, check_). All tools have descriptions ranging 60-180 chars, meeting the 10-1024 char baseline. Input schemas are visible and properly typed (string, number, boolean). However, critical gaps exist: NO output schemas are documented (tools don't describe what they return), error handling lacks recovery guidance, and the rubric's baseline expectation that 100% of A+ tool params have descriptions is NOT met, many parameters lack descriptions entirely (e.g., 'query' in search_cards has a description but others like 'face' in get_card_image rely on minimal context). STDIO-only transport (not remotely accessible) is a hard constraint capping protocol readiness at 50. Definition Quality averages 68 because schemas are incomplete (input-only, no outputs) and descriptions, while present, lack the 'WHEN to use' and 'WHAT it returns' guidance pattern:tool-description demands.
Check if a card is legal in Commander format and get its legality status across all formats
Fetch a deck from Archidekt by deck ID or URL, optionally filter for lands only
Get a list of public decks for a specific Archidekt user with pagination
Get the current list of cards banned in Commander format
Get detailed information about a specific Magic: The Gathering card including rules text, mana cost, type, and more
Get a card image with support for multiple languages, sizes, and card faces; returns base64-encoded image data
No output schemas documented for any of the 19 tools. The rubric requires that 'LLMs need to know what fields to expect so they can plan downstream tool calls and extract the right data.' With no documented return types, agents cannot reason about chaining tools or extracting required fields for follow-up calls.
Many parameters have minimal or no descriptions. The rubric baseline states '100% of A+ tool params have descriptions.' Examples: 'face' param in get_card_image says 'Card face to retrieve: front or back for double-faced cards' but lacks guidance on when it applies (only for two-faced cards); 'bracket' in search_archidekt_decks lacks validation context; 'page_size' across multiple tools lacks range documentation (stated as 'default: 20, max: 100' only for some, missing for others).
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-21 | C | 64 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 23 | - | v1 |
Get current pricing for a Magic: The Gathering card in USD, EUR, and BRL (Brazilian Real via conversion)
Get official rulings and clarifications for a Magic: The Gathering card
Get popular card combos for a color combination from EDHREC
Get EDHREC card recommendations for a specific commander, including high synergy cards, top cards, and statistics
Get the definition of a term from the Magic: The Gathering Comprehensive Rules Glossary
Fetch a deck from Moxfield by URL or deck ID, includes full decklist, metadata, and statistics
Get a list of decks for a specific Moxfield user
Get a specific rule from the Magic: The Gathering Comprehensive Rules by rule number
Search for decks on Archidekt by commander name, with optional power level bracket filtering
Search for Magic: The Gathering cards by name, type, color, or other criteria using Scryfall search syntax
Search for decks on Moxfield by commander name or other criteria, returns popular decks sorted by views/likes
Search the Comprehensive Rules for rules matching a keyword or phrase
Validate a Commander deck for format legality (100 cards, singleton, color identity, banned cards)
No error handling guidance. Tools like search_cards (which queries Scryfall), get_card_details (fuzzy card lookup), and validate_deck (which checks legality) can fail, but no descriptions explain what errors are possible or how the agent should recover. Pattern:recovery-guide requires 'Error responses must tell the LLM what to do next.'
No pagination guidance for list-returning tools. Tools like get_moxfield_user_decks, search_moxfield_decks, and search_archidekt_decks return lists but lack explicit documentation of whether results are truncated, what the total count is, or how to fetch the next page. Pattern:paginated-result requires 'accept page/offset and limit parameters and return a total count or next_cursor.'
get_card_image parameter descriptions do not explain when 'collector_number' is required (stated as 'requires set parameter') but 'set' itself is optional. This creates ambiguous dependencies. Pattern:tool-description requires documenting parameter relationships.
Several tools accept free-form string parameters where enums would improve clarity and prevent hallucination. Examples: 'language' in get_card_image (only 'en' documented but many are valid); 'size' in get_card_image (lists 'small, normal, large, png, art_crop, border_crop' as text, not an enum constraint); 'sort_type' in search_moxfield_decks ('updated', 'views', 'likes' should be an enum, not a free-form string).