chess-support-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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_or_reset_gameA | Create a new game or reset the current one to the initial position. Returns (in result):
Notes:
|
| get_statusA | Get current position metadata for model-friendly planning. Returns (in result):
|
| add_moveA | Apply a move in UCI format if legal. Parameters:
Returns (in result):
Notes:
|
| is_legalA | Check if a UCI move is legal in the current position. Returns (in result):
|
| list_movesA | Return all moves played so far in UCI, ordered from the start of the game. |
| list_moves_detailedA | Return detailed move history. Each item: { ply:int, side:"white"|"black", uci:string, san:string } |
| last_movesA | Return the last N moves in UCI (default 1). Parameters:
|
| last_moves_detailedA | Return the last N moves with details (default 1). Each item: { ply:int, side:"white"|"black", uci:string, san:string }. Parameters:
|
| board_asciiA | Return an ASCII representation of the board from White's perspective. Notes:
|
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 9 tools
Most tools have clearly distinct purposes, but the closely named list_moves/list_moves_detailed and last_moves/last_moves_detailed differ only in detail level, which could cause misselection.
The naming is predominantly verb_noun in snake_case, but deviations like 'is_legal' and 'board_ascii' break the pattern, creating minor inconsistency.
Nine tools is within the typical well-scoped range, though list_moves and last_moves could potentially be consolidated with an optional limit parameter.
Core lifecycle is covered—create/reset, apply move, query status, history—but missing legal move enumeration and FEN import represent notable gaps for an agent.