Skip to main content
Glama
freshlife001

Texas Holdem MCP Server

by freshlife001

login

Access and list all available poker tables by authenticating with a username. Use this to join Texas Holdem games on the MCP server.

Instructions

login and list all tables in the poker game

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes

Implementation Reference

  • Executes the 'login' tool: registers the player with the given name, retrieves player ID, lists available poker tables with details.
    if (request.params.name === "login") {
      response = await sendPokerRequest('register', { name: args?.name });
      view_text = `Logged in as ${args?.name}.\n Your PlayerID: ${response.playerId}.\n Available tables:\n`;
      
      // After login, fetch tables
      const tables = await sendPokerRequest('listTables', {});
      if (tables && tables.length > 0) {
        tables.forEach((table: any, index: number) => {
          view_text += `Table: ${table.name} - TableID: ${table.id} - Players: ${table.players}/${table.maxPlayers} - Blinds: $${table.smallBlind}/$${table.bigBlind}\n`;
        });
      } else {
        view_text += "No tables available. Create one to start playing.";
      }
    } 
  • src/mcpServer.ts:31-41 (registration)
    Registers the 'login' tool in the MCP server's listTools handler, defining its name, description, and input schema.
    {
      name: "login",
      description: "login and list all tables in the poker game",
      inputSchema: {
        type: "object",
        properties: {
          name: { type: "string" },
        },
        required: ['name'],
      },
    },
  • Helper function used by the 'login' handler to send 'register' and 'listTables' requests to the poker server via socket.io.
    function sendPokerRequest(method: string, params: any): Promise<any> {
      return new Promise((resolve, reject) => {
        const request = {
          method,
          params,
          id: Date.now()
        };
        
        //console.log(`[Client] Sending request: ${method}`, params);
        
        socket.emit('action', request, (response: any) => {
          //console.log(`[Client] Received response for ${method}:`, response);
          
          if (response.error) {
            console.error(`[Client] Error in ${method}:`, response.error);
            reject(response.error);
          } else {
            resolve(response.result);
          }
        });
      });
    }
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 mentions 'login' (suggesting authentication) and 'list all tables', but doesn't clarify if this is a read-only operation, what authentication is required, whether it creates a session, or what happens on failure. This leaves significant gaps for a tool with authentication implications.

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?

The description is a single, efficient sentence that front-loads the core actions. However, its dual-purpose nature ('login and list') slightly reduces clarity, but it avoids unnecessary verbosity.

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 no annotations, no output schema, and low schema coverage, the description is incomplete. It doesn't explain the authentication process, return values (e.g., table list format, session tokens), or error handling, which are critical for a tool involving login functionality.

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 schema has 1 parameter with 0% description coverage, so the description must compensate. It doesn't mention the 'name' parameter at all, leaving its purpose (e.g., username, player name, session identifier) completely undocumented. This fails to add meaning beyond the bare schema.

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?

The description states the tool performs two actions: 'login' and 'list all tables in the poker game'. While it specifies the resource (poker game tables), the dual-purpose nature makes it somewhat vague compared to a single, specific verb+resource combination. It doesn't clearly distinguish from siblings like 'get_table_status' or 'join_table'.

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 explicit guidance is provided on when to use this tool versus alternatives. The description implies it might be for initial setup or authentication, but there's no mention of prerequisites, when-not-to-use scenarios, or how it relates to siblings like 'join_table' or 'get_table_status'.

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/freshlife001/mcp_poker'

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