Skip to main content
Glama
tonypan2

Minesweeper MCP Server

by tonypan2

click

Interact with the Minesweeper board by selecting specific cells using row and column coordinates to reveal or flag tiles.

Instructions

Click at a cell on the Minesweeper board

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
colYes
rowYes

Implementation Reference

  • Handler logic for the 'click' tool: sets the URL parameters to reveal the cell at the specified row and column by appending 'reveal=1' and 'pos=row,col' to the game API endpoint.
    } else if (request.params.name === "click") {
      url.searchParams.set("reveal", "1");
      url.searchParams.set("pos", `${row},${col}`);
  • Input schema for the 'click' tool, defining 'row' and 'col' as required number properties.
    inputSchema: {
      type: "object",
      properties: {
        row: { type: "number" },
        col: { type: "number" },
      },
      required: ["row", "col"],
    },
  • src/index.ts:35-46 (registration)
    Registration of the 'click' tool in the ListToolsRequestSchema handler, including name, description, and input schema.
    {
      name: "click",
      description: "Click at a cell on the Minesweeper board",
      inputSchema: {
        type: "object",
        properties: {
          row: { type: "number" },
          col: { type: "number" },
        },
        required: ["row", "col"],
      },
    },
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden but only states the action without disclosing behavioral traits. It doesn't explain what happens when clicking (e.g., reveals cell, may trigger mine, game state changes), safety implications, or error conditions, leaving significant gaps for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero wasted words, front-loading the core action. It's appropriately sized for a simple tool, though brevity contributes to gaps in other dimensions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations, 0% schema coverage, and no output schema, the description is incomplete. It lacks details on behavior, parameters, outcomes, and integration with sibling tools, making it inadequate for safe and effective use by an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate but adds no parameter meaning beyond what the schema provides. It mentions 'cell' which relates to 'row' and 'col', but doesn't explain coordinate systems, valid ranges, or board boundaries, failing to address the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('click') and target ('at a cell on the Minesweeper board'), providing specific verb+resource. However, it doesn't explicitly differentiate from sibling tools like 'flag' or 'unflag' which also operate on board cells, missing full sibling distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like 'flag' or 'unflag', nor does it mention prerequisites such as requiring an active game started via 'start_game'. The description implies usage context but lacks explicit when/when-not instructions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tonypan2/minesweeper-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server