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

Smarter.Poker Model Context Protocol (MCP) Server

Official

calculate_staking_markup_split

Read-onlyIdempotent

Compute tournament staking package value, markup cost per percent, investor share price, breakeven ROI and net payouts for investor and horse from gross cashes.

Instructions

Calculates tournament staking package total value, markup price per %, investor share cost, breakeven ROI % required at the given markup, and net payouts for both investor and horse across a given gross cash amount.

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

Input Schema

NameRequiredDescriptionDefault
markupNoMarkup multiplier applied to the package (e.g. 1.00 to 1.50, default: 1.15).
action_sold_percentNoTotal percentage of action sold by the horse across all backers (default: 50).
gross_cashes_dollarsNoTotal gross tournament cashes and refunds at the end of the package (default: 24000).
investor_share_percentNoPercentage share purchased by an individual investor (default: 10).
package_buyins_dollarsNoTotal face-value buy-ins in the tournament staking package in dollars (default: 10000).
estimated_player_roi_percentNoEstimated true pre-markup player ROI % for EV analysis (default: 25).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.5

TDQS

A3.9/5.0
Behavior4/5

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

Read-only, idempotent, and non-destructive behavior is already fully covered by the annotations, so the description does not need to repeat it. It adds real value by disclosing what the calculation yields (markup price per %, investor share cost, breakeven ROI, net payouts for both parties), which matters because there is no output schema. It does not address how the optional defaults interact or what happens when percentages are inconsistent (for example, sold percent plus retention).

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 with no filler, and the output enumeration is compact. It is somewhat of a run-on list joined by 'and', so scanning the individual computed values takes effort. That is minor, but it is a structural weakness.

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 stateless, all-optional-parameter calculator, the description covers the essential question: what does this return. It also compensates for the absent output schema. Gaps are minor: no note on how the outputs relate (for example, that breakeven ROI is derived from markup) or on behavior with edge-case inputs.

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% and every one of the six parameters already carries unit and default details, so the schema does the heavy lifting. The description mentions the inputs only obliquely (markup, gross cash, investor share) and does not add format or constraint guidance beyond the schema. A baseline 3 is appropriate.

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 (calculates) and a precise resource (tournament staking markup split). It then enumerates the exact quantities returned, so the tool is distinguishable from the other poker calculators by domain alone (staking economics, not odds, ICM, or chop math).

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 use case is implied by the domain and the enumerated outputs, but no explicit 'use when' condition or steering away from any alternative is stated. Since no sibling tool covers staking package math, the practical risk is low, but this remains inference rather than guidance.

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