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

Smarter.Poker Model Context Protocol (MCP) Server

Official

calculate_tournament_chop

Read-onlyIdempotent

Compute final-table deal payouts and compare Malmuth-Harville ICM, proportional Chip Chop, and Save-Amount results with a trophy bonus set aside.

Instructions

Compute final-table deal payouts comparing Malmuth-Harville ICM Chop, proportional Chip Chop, and Save-Amount Chop (setting aside a trophy cash bonus for 1st place).

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": {
      "stacks": "<stacks>",
      "payouts": "<payouts>"
    },
    "name": "calculate_tournament_chop"
  }
}

Input Schema

NameRequiredDescriptionDefault
stacksYesArray of remaining player chip stacks (e.g. [500000, 300000, 200000]).
payoutsYesArray of remaining tournament prize payouts from 1st place down (e.g. [10000, 6000, 4000]).
saveAmountNoOptional dollar amount set aside for the eventual winner in a Save-Amount deal (default: 0).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.3

TDQS

A3.5/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 the safety profile is fully covered. The description adds that three distinct methods are computed and that the save amount is withheld from the pool for 1st place, which is genuinely useful behavioral context. However, it says nothing about the return shape (presumably three parallel payout arrays) or how mismatched stacks/payouts lengths are handled, so a 3 is appropriate.

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 dense sentence that front-loads the action and lists the differentiators without filler. Every clause earns its place, and there is no redundant restatement of the schema.

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?

For a pure calculator with no output schema, the description should say what comes back — e.g. one payout array per method — and whether the stacks and payouts arrays must be the same length. It omits both. The safety and idempotency story is fully carried by annotations, so the missing output/return detail is the main gap.

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%, so all three parameters are already documented with types, defaults, and examples, establishing the baseline of 3. The description contributes only marginally, clarifying that saveAmount belongs conceptually to the Save-Amount method rather than the other two. It adds no format constraints or cardinality rules beyond the schema.

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 (compute) and resource (final-table deal payouts) and enumerates the three methods compared: Malmuth-Harville ICM, Chip Chop, and Save-Amount Chop. It is immediately clear what the tool produces. It stops short of a 5 because it never distinguishes itself from the closely related sibling calculate_icm_payouts, leaving the agent to guess which one to pick.

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 only implied by the phrase 'final-table deal', which signals the correct context (negotiating a chop at the end of a tournament). There is no explicit when-to-use statement, no exclusions, and no pointer to the alternative ICM tool. The agent can infer the scenario but is given no routing rule.

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