Skip to main content
Glama

game_state

Fetch the current public state of a Minesweeper game to track progress, view board layout, and monitor remaining mines.

Instructions

Fetch the public state for a game.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
public_idYes

Implementation Reference

  • The handler for the 'game_state' tool, which extracts the 'public_id' from input and calls rails.getState.
    async (input) => {
      const publicId = requireString(
        (input as { public_id?: unknown })?.public_id,
        "public_id"
      );
      return rails.getState(publicId);
    }
  • The schema definition for the 'game_state' tool.
    inputSchema: {
      type: "object",
      properties: {
        public_id: { type: "string" },
      },
      required: ["public_id"],
    },
  • The registration of the 'game_state' tool via addTool within the createTools function.
    addTool(
      {
        name: "game_state",
        description: "Fetch the public state for a game.",
        inputSchema: {
          type: "object",
          properties: {
            public_id: { type: "string" },
          },
          required: ["public_id"],
        },
      },
      async (input) => {
        const publicId = requireString(
          (input as { public_id?: unknown })?.public_id,
          "public_id"
        );
        return rails.getState(publicId);
      }
    ),
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. While 'Fetch' implies a read-only operation, the description fails to specify the return structure, potential error states (e.g., game not found), rate limits, or what distinguishes 'public' from potentially private game data.

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

Conciseness4/5

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

Single sentence is appropriately front-loaded with no wasted words. However, extreme brevity contributes to information gaps given the lack of supporting documentation in schema or annotations.

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 zero schema coverage, no annotations, and no output schema, the description is insufficient. It omits critical details such as parameter semantics, the specific properties of the returned game state, and behavioral constraints expected of a data-retrieval tool.

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%, requiring the description to compensate. Although the parameter name 'public_id' and phrase 'for a game' together imply this is a game identifier, the description lacks explicit confirmation of what the ID represents, its expected format, or how to obtain it.

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

Purpose3/5

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

States the basic action (fetch) and target (public state for a game) but 'public state' remains vague regarding what specific data is returned. Does not explicitly differentiate from sibling tools like user_games or clarify if this retrieves ongoing game status versus historical data.

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?

Provides no guidance on when to use this tool versus alternatives like user_games or game_open. No mention of prerequisites (e.g., does the game need to be active?) or typical usage patterns.

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/geeknees/minesweeper-mcp'

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