Skip to main content
Glama
Vic563

Minesweeper MCP Server

by Vic563

list_boards

Retrieve all active Minesweeper game boards to track ongoing games and manage gameplay sessions.

Instructions

List all active Minesweeper boards

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler for the 'list_boards' tool within the CallToolRequestSchema switch statement. It calls game.getAllBoards(), formats a descriptive list of active boards including dimensions, mine count, game state, and duration if finished, and returns formatted text content.
    case 'list_boards': {
      const boards = this.game.getAllBoards();
      
      if (boards.length === 0) {
        return {
          content: [
            {
              type: 'text',
              text: 'No active Minesweeper boards found.',
            },
          ],
        };
      }
    
      let message = `Active Minesweeper Boards (${boards.length}):\n\n`;
      for (const board of boards) {
        const duration = board.endTime 
          ? Math.round((board.endTime - board.startTime) / 1000)
          : Math.round((Date.now() - board.startTime) / 1000);
        
        message += `• ${board.id}: ${board.width}x${board.height}, ${board.mineCount} mines, ${board.gameState}`;
        if (board.gameState !== 'playing') {
          message += ` (${duration}s)`;
        }
        message += '\n';
      }
    
      return {
        content: [
          {
            type: 'text',
            text: message,
          },
        ],
      };
    }
  • The tool definition including name, description, and input schema (empty object since no parameters) as part of the tools list returned by ListToolsRequestHandler.
    {
      name: 'list_boards',
      description: 'List all active Minesweeper boards',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Supporting method in MinesweeperGame class that retrieves and returns an array of all active GameBoard instances stored in the internal Map.
    getAllBoards(): GameBoard[] {
      return Array.from(this.boards.values());
    }
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 lists active boards but doesn't describe what 'active' means, whether the list is paginated, sorted, or includes metadata, or any error conditions. This leaves significant gaps in understanding the tool's behavior beyond the basic purpose.

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 that directly states the tool's purpose without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse quickly, which is ideal for a simple listing tool.

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

Completeness3/5

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

Given the tool's simplicity (0 params, no output schema, no annotations), the description is minimally adequate but lacks depth. It doesn't explain what 'active' entails, the format of the returned list, or how it differs from siblings like 'get_board'. For a basic tool, it's passable but could be more informative to fully guide the agent.

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

Parameters4/5

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

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add param info, which is appropriate here, but it could have mentioned implicit constraints (e.g., no filters). Baseline is 4 for zero-param tools, as the schema fully covers the absence of inputs.

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 ('List') and resource ('all active Minesweeper boards'), providing specific verb+resource pairing. However, it doesn't explicitly differentiate from sibling tools like 'get_board' (which might retrieve a single board), leaving some ambiguity about when to use one versus the other.

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 'get_board' or 'create_board'. The description implies it's for listing active boards but doesn't specify scenarios (e.g., overview vs. detailed view) or exclusions, leaving the agent to infer usage from context alone.

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