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

Smarter.Poker Model Context Protocol (MCP) Server

Official

calculate_preflop_isolation_raise

Read-onlyIdempotent

Calculate optimal pre-flop isolation raise sizing, projected heads-up flop pot, and effective stack-to-pot ratio from limpers, position, environment, and stack depth.

Instructions

Calculates optimal pre-flop isolation raise sizing (3BB + 1BB per limper + 1BB OOP tax), projected heads-up flop pot size, and effective stack-to-pot ratio (SPR).

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_preflop_isolation_raise"
  }
}

Input Schema

NameRequiredDescriptionDefault
limpersNoNumber of open-limpers ahead of Hero from 1 to 6 (default: 2).
positionNoHero postflop position relative to the limpers: "IP" (CO/BTN) or "OOP" (SB/BB, default: "IP").IP
environmentNoGame environment: "online" (3BB base open) or "live" (4BB base open, default: "online").online
big_blind_dollarsNoDollar value of 1 Big Blind for live cash conversion (default: 5).
effective_stack_bbNoEffective starting stack in Big Blinds (default: 100).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.5

TDQS

A4.2/5.0
Behavior4/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 safety is covered. The description adds real behavioral value by exposing the deterministic computation (3BB base + 1BB per limper + 1BB OOP tax) and the outputs produced, though it does not state edge behavior such as what happens at the schema's extremes of 1 or 6 limpers.

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

Conciseness5/5

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

A single, front-loaded sentence with no filler — the formula and the returned values are packed in without redundancy. Every clause carries distinct information.

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 five optional parameters, full schema descriptions, and rich annotations, the definition needs only to convey purpose and outputs, which it does; with no output schema, listing raise size, flop pot and SPR is exactly the right compensation. A minor gap is that it never clarifies the relationship between the 'online' 3BB base it cites and the live 4BB base defined in the schema.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns above that by explaining how parameters feed the result — 'per limper' ties to the limpers count and the '1BB OOP tax' ties to the position enum. It does not restate the live 4BB base or dollar conversion, which the schema already documents.

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 names a specific verb and resource ('Calculates optimal pre-flop isolation raise sizing') and then enumerates the exact formula and the three returned quantities (raise size, projected heads-up flop pot, SPR). This is far more specific than a title restatement and lets an agent distinguish it from generic sizing tools like calculate_spr_sizing.

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 scenario is implied by the phrase 'pre-flop isolation raise' facing 'limpers', so an agent can infer this is for the limper-isolation spot. However, there is no explicit when-to-use/when-not guidance and no mention of alternative tools (e.g., get_preflop_chart or calculate_spr_sizing) that a caller might confuse it with.

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