Minesweeper 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_gameB | Start a new game of Minesweeper |
| clickC | Click at a cell on the Minesweeper board |
| flagC | Place a flag at a cell on the Minesweeper board |
| unflagC | Remove the flag at a cell on the Minesweeper board |
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 4 tools
Each tool has a clearly distinct purpose: click interacts with cells, flag marks them, unflag removes marks, and start_game initiates play. There is no overlap or ambiguity between these actions in the Minesweeper context.
All tool names follow a consistent verb-based pattern (click, flag, start_game, unflag) with clear, descriptive actions. The naming is uniform and predictable throughout the set.
Four tools are well-scoped for a Minesweeper server, covering essential gameplay actions (click, flag, unflag) and game initialization (start_game). This count is appropriate and each tool earns its place without being excessive or insufficient.
The tool set provides complete coverage for basic Minesweeper operations: starting a game, interacting with cells (clicking and flagging), and managing flags (unflagging). There are no obvious gaps for the core gameplay loop.