pyplai-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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_gamesA | List the games you can play, their move format and the algorithms available for each. |
| get_rulesA | Full rules and move notation of a game, in Markdown. The same text as the rules://{game} resource. |
| new_gameB | Start a game against a pyplAI algorithm. If the opponent moves first, it has already moved in the returned state. |
| get_stateB | Show the board as you see it, your legal moves and what has happened so far. |
| play_moveB | Play a move. The opponent replies straight away, so the returned state is your next turn (or the end of the game). |
| analyze_positionA | Rank your legal moves with a search from the current position. It only uses information you have. |
| end_gameC | Forget a game you no longer need. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| play_game | Play a full game, using the search tools to choose and explain each move. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct action in the game lifecycle (list, rules, new, play, state, analyze, end) with little true overlap. The only mild ambiguity is between get_state (shows legal moves) and analyze_position (ranks legal moves), but descriptions make the distinction clear.
All seven tools follow a consistent snake_case verb_noun pattern (list_games, get_rules, play_move, new_game, get_state, analyze_position, end_game). No mixed conventions or vague verb styles.
Seven well-scoped tools fit the game-playing domain cleanly, each earning its place with a distinct role. Neither thin nor bloated.
The surface covers a full game lifecycle: discover games, read rules, start, play, inspect state, analyze, and clean up. Minor gaps like undo/resign or move history rollback exist but are workable around.