pure-llm-chess-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| new_gameC | Create a game with the selected chess variant and options. |
| get_stateA | Return the current position, turn, and assessment. Set ascii to include a text board, or unicode to include a board with Unicode pieces where supported. |
| play_moveA | Validate and apply one submitted move. Set allow_illegal to force a from/to move when it is illegal; the result reports legal and applied separately. |
| edit_boardC | Edit board cells, including adding, removing, or replacing pieces, plus optional turn or rule state. |
| import_gameA | Import JSON full history/state, a FEN position snapshot, or a supported PGN mainline and return a new game ID. FEN/PGN imports accept variant options; JSON restores its saved options. |
| export_gameB | Export full JSON history/state, a FEN position snapshot, or a supported PGN mainline. |
| list_variantsA | List installed variants, their options and move schemas, and supported import/export formats. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct action: creating, inspecting, moving, editing, exporting, importing, and listing variants. There is no meaningful overlap between them.
All tool names follow a consistent verb_noun pattern (new_game, get_state, play_move, edit_board, export_game, import_game, list_variants). The naming is uniform and predictable.
Seven tools is well-scoped for a chess MCP server: it covers game lifecycle, state inspection, move execution, board editing, import/export, and variant discovery without unnecessary bloat.
The tool surface covers the full chess workflow: create, inspect, move, edit, import/export, and discover variants. No obvious dead ends or missing core operations for the stated purpose.