Texas Holdem MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| loginC | login and list all tables in the poker game |
| join_tableC | Join a poker table |
| get_table_statusC | Get the current status of a poker table |
| leave_tableC | Leave a poker table |
| action_checkD | do action check |
| action_foldD | do action fold |
| action_betD | do action bet |
| action_raiseD | do action raise |
| action_callD | do action call |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Every tool has a clearly distinct purpose with no ambiguity. The five action_* tools each represent a specific poker move (bet, call, check, fold, raise), while the other four tools handle table management and login functions. There is no overlap in functionality between these categories.
The naming is mostly consistent with a clear verb_noun pattern, but there is one minor deviation. The action_* tools follow a consistent 'action_verb' format, and get_table_status, join_table, and leave_table follow a 'verb_noun' pattern. However, 'login' breaks this pattern by being a single verb without a noun, though it's still readable.
With 9 tools, this server is well-scoped for a Texas Hold'em poker domain. It covers essential actions (bet, call, check, fold, raise), table management (join, leave, get status), and authentication (login), with each tool earning its place without being excessive or insufficient.
The tool surface is largely complete for basic poker gameplay, covering key actions and table lifecycle. However, there are minor gaps, such as no tools for creating or listing tables, which might be inferred from 'login' but aren't explicitly provided, potentially requiring workarounds for full table management.