MCP server for Magic: The Gathering card database queries. Implements standard JSON-RPC MCP protocol with tools for searching cards and retrieving collection statistics from MySQL/Memory persistence layers.
Critical gaps across all dimensions. Tool descriptions are minimal (6-8 chars), far below the 10-1024 char baseline. search_cards has a basic schema with one parameter, but get_statistics has an empty properties object with no parameters documented. No output schemas documented. Parameter descriptions are absent or trivial. No error handling guidance, no recovery paths, no input validation hints. The server implements basic JSON-RPC tool listing and execution but lacks production-grade tool design patterns.
Ver stats
Busca cartas en MySQL.
Tool descriptions critically short (6-8 chars). 'Busca cartas en MySQL' and 'Ver stats' provide no context for LLM selection, when to use the tool, or what it returns. Baseline is 10-1024 chars; these are 1-2% of minimum.
get_statistics has empty input schema (no properties, no required fields). This tool's schema is completely undocumented.
No output schemas documented. LLMs cannot plan downstream calls or extract data. search_cards returns JSON array of cards; get_statistics returns a text string. Neither structure is declared in tool definitions.
search_cards parameter 'name' lacks actionable description. Current: 'Nombre o lista de nombres.' Does not specify format (comma-separated? JSON array?), length limits, or examples.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 35 | 2026-07-28+ | v2 |
No error handling guidance. ExecuteToolAsync catches exceptions and returns raw ex.Message. LLMs receive 'Object reference not set to an instance of an object' with no recovery path. Per pattern, errors must guide next steps.