Skip to main content
Glama

user_games

Retrieve public Minesweeper games for a specific user by providing their user slug to view game history and current status.

Instructions

List public games for a user slug.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_slugNo

Implementation Reference

  • The handler function for the user_games tool, which validates the user_slug and calls rails.listGames.
    async (input) => {
      const userSlug = requireStringOrEnv(
        (input as { user_slug?: unknown })?.user_slug,
        "user_slug",
        process.env.MINESWEEPER_USER_SLUG,
        "MINESWEEPER_USER_SLUG"
      );
      return rails.listGames(userSlug);
    }
  • The tool definition for user_games, including the name, description, and input schema.
    {
      name: "user_games",
      description: "List public games for a user slug.",
      inputSchema: {
        type: "object",
        properties: {
          user_slug: { type: "string" },
        },
      },
  • The registration of the user_games tool within the createTools function.
    addTool(
      {
        name: "user_games",
        description: "List public games for a user slug.",
        inputSchema: {
          type: "object",
          properties: {
            user_slug: { type: "string" },
          },
        },
      },
      async (input) => {
        const userSlug = requireStringOrEnv(
          (input as { user_slug?: unknown })?.user_slug,
          "user_slug",
          process.env.MINESWEEPER_USER_SLUG,
          "MINESWEEPER_USER_SLUG"
        );
        return rails.listGames(userSlug);
      }
    ),
Behavior2/5

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

With no annotations to provide safety hints, the description carries full behavioral burden. It only discloses the 'public' visibility filter, omitting pagination behavior, error handling (e.g., invalid slug), authentication requirements, and return structure.

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?

Extremely brief at six words. While efficient, the brevity is insufficient to cover behavioral transparency and parameter gaps given the complete lack of annotations and schema descriptions.

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?

Covers the basic operation for a single-parameter query tool, but remains incomplete regarding error scenarios, response format, and the distinction between 'public' and private games.

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?

Schema coverage is 0% with no parameter descriptions. The description adds semantic meaning by identifying the parameter as a 'user slug' (vs an ID or username), but provides no format constraints, examples, or validation rules to fully compensate for the schema 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?

States a specific verb (List), resource (public games), and scope (for a user slug). Distinguishes implicitly from sibling game-operation tools (game_chord, game_end) by focusing on user-centric game retrieval, though lacks explicit 'use this when' differentiation.

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 on when to use this versus user_start or game_state. No mention of prerequisites (e.g., whether the user must exist) or workflow position.

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