Chess MCP 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_profileB | Get the public profile for a Chess.com player by username. |
| get_chess_player_statsB | Get the stats for a Chess.com player by username. |
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 a player's public profile, the other retrieves their stats. There is no overlap or ambiguity.
Both tools follow the exact same pattern: get_chess_player_ followed by a specific noun (profile, stats). This is consistent and predictable.
With only two tools, the server feels thin. While they cover a focused player-info domain, the broader chess context suggests more tools could be expected, making the count borderline.
The tools cover the main player profile and stats endpoints, but the server is named 'Chess MCP Server,' implying a wider scope. Missing tools for games, tournaments, or other chess data create notable gaps.