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

Smarter.Poker Model Context Protocol (MCP) Server

Official

lookup_hand_matchup

Read-onlyIdempotent

Get exact preflop win/tie/loss equity, combinatorics, flop texture shifts, and 100BB vs 25BB stack-off EV for canonical Texas Hold'em hand-vs-hand matchups.

Instructions

Look up exact preflop win/tie/loss equity, combinatorics, flop texture equity shifts, and 100BB vs 25BB stack-off EV notes for canonical Texas Hold'em hand-vs-hand matchups (e.g. "aa-vs-kk", "aks-vs-qq", "jj-vs-ako", "55-vs-kts").

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": "lookup_hand_matchup"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoMatchup slug (e.g. "aa-vs-kk", "aks-vs-qq", "jj-vs-ako", "55-vs-kts") or omit to list all 25 canonical matchups.
handANoOptional first hand code (e.g. "AA", "AKs", "QQ").
handBNoOptional second hand code (e.g. "KK", "QQ", "AKo").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.5
    • changedInput schema / properties / slug / description
      Previous value: -"Matchup slug (e.g. \"aa-vs-kk\", \"ak-vs-qq\", \"jj-vs-aks\") or omit to list all 25 canonical matchups."New value: +"Matchup slug (e.g. \"aa-vs-kk\", \"aks-vs-qq\", \"jj-vs-ako\", \"55-vs-kts\") or omit to list all 25 canonical matchups."
  2. Addedv1.0.3

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered. The description adds real value by disclosing the categories of returned content (equity, combinatorics, flop texture equity shifts, 100BB vs 25BB stack-off EV notes), which matters because there is no output schema. It stops short of stating output format, size, or units, so it is a moderate rather than rich contribution.

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?

One front-loaded sentence that leads with the verb and resource before piling on the return categories. Dense but every clause carries information; the only redundancy is the slug examples, which duplicate the schema.

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?

For a read-only lookup with three optional parameters and no output schema, the description does the heavy lifting by enumerating the returned data categories and noting the stack-depth dimension. Missing only edge-case behavior (partial handA/handB, invalid slug) to be fully complete.

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%, so role and example values for slug, handA and handB are already documented in the schema. The description reuses the same slug examples without clarifying precedence between slug and handA/handB or what a partial handA-only call yields, so it adds little beyond structured data. Baseline 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?

A specific verb ("Look up") paired with a precisely bounded resource ("canonical Texas Hold'em hand-vs-hand matchups") and an enumeration of what is returned: equity, combinatorics, flop texture shifts, stack-off EV notes. Concrete slug examples ("aa-vs-kk", "aks-vs-qq") make the scope unmistakable and separate it from single-hand lookups or generic odds calculators.

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?

The definition implies usage well by naming the exact matchup format it serves, but never states when to prefer it over siblings such as lookup_starting_hand or calculate_poker_odds, nor any exclusions. The 'omit slug to list all 25' behavior is guidance, but it already lives in the schema rather than adding new routing advice.

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