MCP Chess Server
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 |
|---|---|
| get_chess_player_profileC | Get the public profile for a Chess.com player by player_name. |
| get_chess_player_statsC | Get the stats for a Chess.com player by player_name. |
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 2 tools
The two tools have clearly distinct purposes: one retrieves public profile information, the other retrieves stats. There is no overlap or ambiguity.
Both tools follow a consistent 'get_chess_player_*' pattern, making it easy to infer their functionality from their names.
Two tools is minimal, but for a server focused solely on retrieving Chess.com player data, it could be acceptable. However, it feels thin compared to typical API coverage.
The server covers profile and stats, but lacks other common operations like listing games or tournaments. There are notable gaps for a full player information server.