minesweeper-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | The logging level (e.g., debug, info, warn, error). | info |
| REQUEST_TIMEOUT_MS | No | The request timeout in milliseconds. | 10000 |
| MINESWEEPER_BASE_URL | Yes | The base URL for the Minesweeper API (e.g., https://example.com). End without a slash. | |
| MINESWEEPER_BEARER_TOKEN | Yes | The bearer token issued by the Rails backend for authentication. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| user_startC | Start a new game for a user slug. |
| game_stateC | Fetch the public state for a game. |
| game_openC | Open a cell in a game. |
| game_flagC | Toggle a flag on a cell. |
| game_chordC | Chord a cell in a game. |
| game_endC | End a game. |
| user_gamesC | List public games for a user slug. |
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 has a clearly distinct purpose with no ambiguity: chord, end, flag, open, state, list games, and start game are all unique actions in the Minesweeper domain. The descriptions clearly differentiate between game manipulation actions (chord, flag, open), game lifecycle actions (end, start), and query actions (state, list).
All tools follow a perfectly consistent verb_noun pattern with 'game_' or 'user_' prefixes indicating the resource type. The naming is systematic and predictable: game_chord, game_end, game_flag, game_open, game_state, user_games, user_start. This consistency makes the tool set easy to understand and navigate.
With 7 tools, this is well-scoped for a Minesweeper game server. Each tool earns its place by covering essential operations: starting/ending games, cell interactions (open, flag, chord), state retrieval, and game listing. The count is neither too thin nor bloated, perfectly matching the domain's requirements.
The tool surface provides complete coverage for Minesweeper gameplay. It includes all core operations: starting a game (user_start), ending it (game_end), cell interactions (open, flag, chord), state monitoring (game_state), and discovery (user_games). There are no obvious gaps—agents can fully manage the game lifecycle and player interactions without dead ends.