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

Smarter.Poker Model Context Protocol (MCP) Server

Official

calculate_home_game_chip_set

Read-onlyIdempotent

Calculates optimal starting chip denominations per player and total physical chips needed for a home cash game or tournament with 2 to 30 players.

Instructions

Calculates optimal starting chip denomination tubes per player (4 to 5 denominations) and total physical chips required for a home cash game or tournament of players (2-30).

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

Input Schema

NameRequiredDescriptionDefault
formatNoHome game format: "cash" or "tournament" (default: "cash").cash
presetNoDenomination preset: "cash-25-50" ($0.25/$0.50), "cash-1-2" ($1/$2), "t10000" (T10,000), or "t25000" (T25,000).cash-1-2
playersNoNumber of players in the home game from 2 to 30 (default: 8).
chip_set_sizeNoTotal chip case size (300, 500, or 1000, default: 500).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.5

TDQS

A4/5.0
Behavior4/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 the safety profile is covered. The description adds genuine value beyond them by disclosing the computation's shape — per-player tube denominations (4-5) plus total physical chips — which is the key behavioral fact for a tool with no output schema. It stops short of noting whether infeasible player/chip_set_size combinations are rejected or adjusted.

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 zero filler: verb first, then outputs, then operating constraints. Every clause contributes information an agent would otherwise have to guess.

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 no output schema, the description takes on the job of explaining what comes back and does so at a useful level (denominations per player, total chips). For a 4-parameter, fully-defaulted, read-only calculator this is close to sufficient; only edge-case behavior (infeasible combinations, how presets map to denominations) is unaddressed.

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% with two enums fully enumerated, so the schema already carries parameter meaning and the baseline of 3 applies. The description restates the 2-30 player bound already documented in the players parameter and adds no format, preset-selection, or chip_set_size interaction detail beyond the schema.

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?

States a specific verb ("Calculates") and a precisely scoped resource: optimal starting chip denomination tubes per player plus total physical chips. It names the two outputs (per-player denomination breakdown and total chip count) and the supported range (4-5 denominations, 2-30 players), so an agent can tell exactly what it produces and that no sibling tool covers chip-set planning.

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 domain (home cash game or tournament) is implied by the description and encoded in the format enum, so an agent can infer when this applies. However, there is no explicit when-to-use statement, no exclusions, and no guidance on choosing between presets or reconciling players vs. chip_set_size — those decisions are left entirely to the schema.

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