Skip to main content
Glama
Smarter.Poker Model Context Protocol (MCP) Server

Smarter.Poker Model Context Protocol (MCP) Server

Official

calculate_poker_odds

Read-onlyIdempotent

Compute exact win, tie, and equity probabilities for Texas Hold'em and Omaha hands, including board runouts, to evaluate poker decisions.

Instructions

Calculate exact equity, win, and tie probabilities for Texas Hold'em and Omaha hands with board runouts.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "hands": "<hands>"
    },
    "name": "calculate_poker_odds"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameNoPoker game variant (default: nlhe for No-Limit Texas Hold'em).nlhe
boardNoOptional community board cards (e.g. ["Jh", "Ts", "2c"] or "Jh,Ts,2c").
handsYesArray of player hands (e.g. [["Ah", "Kd"], ["Qc", "Qd"]] or ["AhKd", "QcQd"]).
iterationsNoMonte Carlo simulation iterations (default: 10000, max: 50000).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered and the description only needs to add computational context. It does add the notion of enumerating board runouts and the supported variants, but the word 'exact' misstates behavior: the schema exposes a Monte Carlo 'iterations' parameter (default 10000, max 50000), so results are simulated, not exact, and the description says nothing about accuracy trade-offs or runtime cost. That gap is meaningful for an agent deciding how to call it.

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?

A single front-loaded sentence with no filler, and the core verb and outputs lead. It is appropriately sized, though the space spent on the inaccurate word 'exact' could have gone to routing or accuracy guidance.

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?

With no output schema, the description should be a bit more explicit about the returned shape (per-hand equity/win/tie split) and about multiway limits and simulated-vs-exact behavior. It gestures at the outputs correctly but leaves an agent guessing on result structure and accuracy, which is a moderate gap for a four-parameter compute tool.

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 description coverage is 100% and each parameter is documented in the schema, so baseline 3 applies. The description adds only the high-level concepts (game variants, board runouts) and gives no extra detail on hand/board string formatting or the significance of the iterations cap beyond what the schema already states.

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?

The description names a specific verb and outputs — 'Calculate exact equity, win, and tie probabilities' — plus the supported games (Texas Hold'em, Omaha) and the scenario (board runouts). That is enough for an agent to distinguish it from sibling calculators like calculate_pot_odds_and_mdf or calculate_draw_outs, though it never explicitly names an alternative to route away from.

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?

There is no when-to-use or when-not-to-use guidance, no mention of the alternative equity/odds tools in the sibling set, and no prerequisites (e.g. minimum number of hands, whether hole cards must be distinct). Usage is only inferable from the name and the phrase 'board runouts'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.