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

Smarter.Poker Model Context Protocol (MCP) Server

Official

calculate_draw_outs

Read-onlyIdempotent

Compute exact poker draw probabilities for 1–21 clean outs across flop and turn, including Rule of 4 and 2 error and break-even pot odds.

Instructions

Compute exact hypergeometric poker draw probabilities (Turn %, River %, Flop-to-River %), Rule of 4 and 2 approximation error, and required break-even pot odds for 1 to 21 clean outs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "calculate_draw_outs"
  }
}

Input Schema

NameRequiredDescriptionDefault
outsNoNumber of clean unseen outs from 1 to 21 (default: 9).
streetNoCurrent street: "flop" (2 cards to come, 47 unseen) or "turn" (1 card to come, 46 unseen, default: "flop").flop

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.3

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered. The description adds value beyond them by enumerating the computed outputs (including the Rule of 4/2 error term) and the supported out-count range, which explains what the caller receives given no output schema. It stops short of stating behavior outside the 1-21 range or precision/rounding conventions.

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 that leads with the verb and stays on-topic with no filler. The output list is dense but each item is a distinct computed quantity, though the enumeration format is slightly harder to scan than a short structured list would be.

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

Completeness4/5

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

With only two optional, fully documented parameters and rich annotations, the definition covers what is needed: the computed outputs substitute for the absent output schema and the input range is stated. The only gap is guidance on choosing between this and the broader odds/pot-odds calculators.

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 100%, with both 'outs' and 'street' fully described including enum meanings and unseen-card counts. The description reinforces 'clean outs' and the 1-21 bound but adds no syntax, edge-case, or validation semantics beyond what the schema already states, so the baseline of 3 applies.

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

Purpose5/5

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

The description opens with a specific verb ('Compute') and a precise resource ('hypergeometric poker draw probabilities'), then enumerates the exact quantities produced: Turn %, River %, Flop-to-River %, Rule of 4/2 approximation error, and break-even pot odds. The scope '1 to 21 clean outs' further pins down what the tool does, making it clearly distinguishable from general odds or pot-odds siblings.

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

Usage Guidelines3/5

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

Usage is implied by the content (draw probabilities for a given number of outs), but there is no explicit statement of when to choose this over calculate_poker_odds or calculate_pot_odds_and_mdf, nor any exclusion. An agent can infer the use case but must reason about sibling selection on its own.

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