Skip to main content
Glama
tonypan2

Minesweeper MCP Server

by tonypan2

unflag

Remove a flag from a specified cell on the Minesweeper board. Requires row and column inputs to identify the target cell for action.

Instructions

Remove the flag at a cell on the Minesweeper board

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
colYes
rowYes

Implementation Reference

  • Handler logic for the 'unflag' tool: sets URL parameters 'unflag=1' and 'pos=row,col' before fetching the updated game board image from the external game server.
    } else if (request.params.name === "unflag") {
      url.searchParams.set("unflag", "1");
      url.searchParams.set("pos", `${row},${col}`);
  • Input schema definition for the 'unflag' tool, specifying required numeric 'row' and 'col' parameters.
    inputSchema: {
      type: "object",
      properties: {
        row: { type: "number" },
        col: { type: "number" },
      },
      required: ["row", "col"],
    },
  • src/index.ts:59-70 (registration)
    Registration of the 'unflag' tool in the ListTools response, including name, description, and input schema.
    {
      name: "unflag",
      description: "Remove the flag 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 the full burden of behavioral disclosure. It states the tool removes a flag, implying a mutation, but doesn't cover critical aspects like whether this requires a game in progress, what happens if no flag exists at the cell, error conditions, or side effects. This leaves significant gaps in understanding the tool's behavior.

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, clear sentence that directly states the tool's purpose without any unnecessary words. It is front-loaded and efficiently conveys the core action, making it easy to parse and understand quickly.

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?

Given the complexity of a game interaction tool with no annotations, no output schema, and low schema coverage, the description is incomplete. It doesn't address key contextual elements like game state requirements, error handling, or what happens after flag removal, making it inadequate for safe and effective use by an 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?

The input schema has 0% description coverage, with parameters 'row' and 'col' undocumented. The description mentions 'a cell' but doesn't explain what 'row' and 'col' represent (e.g., zero-indexed coordinates, board boundaries), failing to compensate for the schema's lack of detail and leaving parameters ambiguous.

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 ('Remove the flag') and the target ('at a cell on the Minesweeper board'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'flag' (which presumably adds flags) or 'click' (which interacts with cells differently), keeping it from a perfect score.

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?

The description implies usage when a flag needs to be removed from a cell, but it offers no guidance on when to use this tool versus alternatives like 'click' or 'flag', nor does it mention prerequisites such as needing an active game or valid coordinates. This lack of explicit context limits its helpfulness.

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