An MCP server that provides chess game functionality with board state management, move execution, and interactive UI visualization
The Chess MCP Server has 3 tools with inconsistent quality. Two chess-specific tools (chess_get_board_state, chess_move) are reasonably well-designed with clear names and basic descriptions, but lack comprehensive parameter documentation and output schema specifications. A third tool (add_numbers) appears to be a workshop example unrelated to the server's core domain. Overall naming follows verb-noun conventions, but descriptions lack the depth and guidance expected in production tools. Parameter types are defined via Zod but not all descriptions explain constraints or dependencies. Output schemas are not documented, responses include both text and UI resources without explicit schema contracts. Error handling is minimal; no guidance on what to do if a move is invalid or a game state is corrupted. The server uses HTTP (good for transport), but relies on session-based state management (sessionId) which introduces stateful behavior inconsistent with modern MCP stateless patterns.
A tool to add two numbers
Get the current state of the chess board
Make a move in standard algebraic notation (e.g., e4, Nf3, O-O)
Output schemas are not documented. Tools return a mix of TextContent and UI resources without specifying the exact structure, field names, or when each is included. LLMs cannot plan downstream operations without knowing the response contract.
chess_move parameter 'move' lacks constraint documentation. Description mentions 'standard algebraic notation' and 'new' as special case, but does not specify valid move formats, length limits, or what happens if an invalid move is provided. No enum or regex pattern constraint.
Error handling is absent. chess_move calls game.move(move.trim()) with no try-catch or validation. If move is invalid, the error is not caught or explained to the LLM, the tool will fail silently or throw an unhandled exception.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 56 | <=2025-11-25 | v2 |
| 2026-03-09 | F | 45 | - | v1 |
chess_get_board_state has an empty input schema ({}). This is valid but offers no validation hook. If the tool ever needs parameters in the future (e.g., board_view_type), the schema must be extended.
Session-based state management (ctx.sessionId) violates modern MCP stateless request handling. Each request should be self-contained; stateful sessions via Mcp-Session-Id were removed from the spec in 2025. Game state should be passed as a parameter or resource URI, not stored server-side.
add_numbers tool is present in workshop/step1 but unrelated to the Chess server's primary domain. This suggests incomplete cleanup or unclear scope definition. A production server should not ship with example tools.