Skip to main content
Glama
Vic563

Minesweeper MCP Server

by Vic563

delete_board

Remove a Minesweeper board from the game server by specifying its unique board ID to manage your saved games.

Instructions

Delete a Minesweeper board

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardIdYesID of the board to delete

Implementation Reference

  • MCP tool handler for 'delete_board': extracts boardId from arguments, calls MinesweeperGame.deleteBoard, and returns success/error text response.
    case 'delete_board': {
      const { boardId } = args as { boardId: string };
      const deleted = this.game.deleteBoard(boardId);
    
      return {
        content: [
          {
            type: 'text',
            text: deleted
              ? `Successfully deleted board '${boardId}'.`
              : `Board '${boardId}' not found.`,
          },
        ],
      };
    }
  • Core implementation of board deletion: removes the board from the internal boards Map.
    deleteBoard(boardId: string): boolean {
      return this.boards.delete(boardId);
    }
  • Tool schema definition: specifies name, description, and input schema requiring a 'boardId' string.
    {
      name: 'delete_board',
      description: 'Delete a Minesweeper board',
      inputSchema: {
        type: 'object',
        properties: {
          boardId: {
            type: 'string',
            description: 'ID of the board to delete',
          },
        },
        required: ['boardId'],
      },
    },
  • src/index.ts:46-166 (registration)
    Registers all tools including 'delete_board' by handling ListToolsRequestSchema and returning the tools list.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: [
          {
            name: 'create_board',
            description: 'Create a new Minesweeper board with specified dimensions and mine count',
            inputSchema: {
              type: 'object',
              properties: {
                id: {
                  type: 'string',
                  description: 'Unique identifier for the board',
                },
                width: {
                  type: 'number',
                  description: 'Width of the board (number of columns)',
                  minimum: 1,
                  maximum: 50,
                },
                height: {
                  type: 'number',
                  description: 'Height of the board (number of rows)',
                  minimum: 1,
                  maximum: 50,
                },
                mineCount: {
                  type: 'number',
                  description: 'Number of mines to place on the board',
                  minimum: 0,
                },
              },
              required: ['id', 'width', 'height', 'mineCount'],
            },
          },
          {
            name: 'reveal_cell',
            description: 'Reveal a cell on the Minesweeper board',
            inputSchema: {
              type: 'object',
              properties: {
                boardId: {
                  type: 'string',
                  description: 'ID of the board',
                },
                x: {
                  type: 'number',
                  description: 'X coordinate (column) of the cell to reveal',
                  minimum: 0,
                },
                y: {
                  type: 'number',
                  description: 'Y coordinate (row) of the cell to reveal',
                  minimum: 0,
                },
              },
              required: ['boardId', 'x', 'y'],
            },
          },
          {
            name: 'flag_cell',
            description: 'Flag or unflag a cell on the Minesweeper board',
            inputSchema: {
              type: 'object',
              properties: {
                boardId: {
                  type: 'string',
                  description: 'ID of the board',
                },
                x: {
                  type: 'number',
                  description: 'X coordinate (column) of the cell to flag',
                  minimum: 0,
                },
                y: {
                  type: 'number',
                  description: 'Y coordinate (row) of the cell to flag',
                  minimum: 0,
                },
              },
              required: ['boardId', 'x', 'y'],
            },
          },
          {
            name: 'get_board',
            description: 'Get the current state and visual representation of a Minesweeper board',
            inputSchema: {
              type: 'object',
              properties: {
                boardId: {
                  type: 'string',
                  description: 'ID of the board to display',
                },
              },
              required: ['boardId'],
            },
          },
          {
            name: 'list_boards',
            description: 'List all active Minesweeper boards',
            inputSchema: {
              type: 'object',
              properties: {},
            },
          },
          {
            name: 'delete_board',
            description: 'Delete a Minesweeper board',
            inputSchema: {
              type: 'object',
              properties: {
                boardId: {
                  type: 'string',
                  description: 'ID of the board to delete',
                },
              },
              required: ['boardId'],
            },
          },
        ] as Tool[],
      };
    });
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 'Delete' which implies a destructive mutation, but doesn't clarify if this is permanent, requires confirmation, or has side effects (e.g., affecting other tools). More context on behavioral traits is needed for safe use.

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 waste, clearly front-loading the action and resource. It's appropriately sized for a simple tool, making it easy to parse 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 tool's destructive nature, lack of annotations, and no output schema, the description is incomplete. It doesn't address critical aspects like return values, error conditions, or safety warnings, which are essential for a deletion tool in this context.

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

Parameters3/5

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

The schema description coverage is 100%, with the parameter 'boardId' fully documented in the schema. The description doesn't add any meaning beyond what the schema provides, such as format examples or constraints, so it meets the baseline for high schema coverage.

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 verb ('Delete') and resource ('a Minesweeper board'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'create_board' or 'get_board' beyond the obvious action difference, missing explicit comparison.

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, such as whether deletion is irreversible or requires specific conditions. The description lacks context about prerequisites or exclusions, leaving usage unclear beyond the basic action.

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

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/Vic563/mindsweeper-mcp'

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