Skip to main content
Glama
freshlife001

Texas Holdem MCP Server

by freshlife001

action_fold

Fold a player's hand in a Texas Holdem poker game using the MCP server API. Specify the player ID and table ID to execute the fold action.

Instructions

do action fold

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
player_idYes
table_idYes

Implementation Reference

  • Executes the 'action_fold' tool by sending a 'performAction' request with action 'fold' to the poker server, then polls for updated table state and formats the response.
    else if (request.params.name === "action_fold") {
      response = await sendPokerRequest('performAction', { 
        playerId: args?.player_id,
        tableId: args?.table_id,
        action: 'fold' 
      });
      view_text = `Player ${args?.player_id} action: Fold\n Game state:\n`;
      
      // Get updated table state
      view_text += await pollUntilPlayerActive(args?.player_id, args?.table_id);
    } 
  • Registers the 'action_fold' tool in the list of available tools, including its description and input schema.
    {
      name: "action_fold",
      description: "do action fold",
      inputSchema: {
          type: "object",
          properties: {
            player_id: { type: "string" },
            table_id: { type: "string" },
          },
          required: ["player_id", "table_id"],
      },
    },
  • Defines the input schema for the 'action_fold' tool, requiring player_id and table_id as strings.
    inputSchema: {
        type: "object",
        properties: {
          player_id: { type: "string" },
          table_id: { type: "string" },
        },
        required: ["player_id", "table_id"],
Behavior1/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'do action fold' reveals nothing about whether this is a read or write operation, what permissions are required, whether it's destructive, what side effects occur, or what the response looks like. This is completely inadequate for a tool that appears to modify game state.

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

Conciseness2/5

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

While technically concise with three words, this is under-specification rather than effective brevity. The description fails to convey essential information that would help an agent use the tool correctly. Every word should earn its place, but here the words don't provide meaningful guidance.

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

Completeness1/5

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

Given the complexity implied by the tool name (game action), zero annotations, undocumented parameters, no output schema, and multiple similar sibling tools, this description is completely inadequate. It provides none of the contextual information needed to understand when and how to use this tool effectively.

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

Parameters1/5

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

With 0% schema description coverage for both parameters (player_id and table_id), the description provides zero information about what these parameters mean, their format, or their purpose. 'do action fold' doesn't mention parameters at all, leaving the agent with completely undocumented inputs.

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

Purpose2/5

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

The description 'do action fold' is a tautology that essentially restates the tool name with minimal added meaning. While it implies this tool performs a 'fold' action in some context (likely poker/gaming), it lacks specificity about what resource or system it operates on and doesn't distinguish it from sibling tools like action_bet or action_call.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides absolutely no guidance about when to use this tool versus alternatives. With multiple action_* siblings (bet, call, check, raise) and other table management tools, there's no indication of appropriate contexts, prerequisites, or exclusions for using action_fold.

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