Skip to main content
Glama

GambleMath — Casino RTP, Bonus EV & UKGC Register Lab

audit_parlay_and_cashout

Calculate multi-leg parlay compounded bookmaker hold and Early Cash-Out vs manual hedge equity.

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

Input Schema

NameRequiredDescriptionDefault
legsNo
stakeUsdNo
cashoutOfferUsdNo
lastLegFairOddsNo
ticketPayoutUsdNo
isSameGameParlayNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the entire behavioral burden. It does not say whether this is a pure computation with no side effects, whether any bookmaker/account context or authentication is required, or whether the numbers returned are a recommendation versus a set of comparative figures. For a six-parameter financial calculation with zero annotation coverage, that is a substantial gap.

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 sentence with no filler, and the core computation is front-loaded. It is dense with domain jargon but not padded; the only cost is that packing two comparisons into one clause makes it slightly harder to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, no annotations, and all six parameters are optional, yet the description never says what happens when inputs are omitted or what the calculation returns. For a numeric audit tool of this complexity, an agent would need to guess both the required input combination and the shape of the result.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for six undocumented parameters. It gestures at the underlying concepts ('multi-leg', 'Early Cash-Out', 'manual hedge equity') but never maps them to leg count, stake, cash-out offer, fair odds, or ticket payout, and gives no units or currency conventions. The mapping is left entirely to inference from parameter names.

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 uses a specific verb ('Calculate') with a specific domain resource ('multi-leg parlay compounded bookmaker hold and Early Cash-Out vs manual hedge equity'). That clearly separates it from the siblings (slot RTP, domain lookup, bonus EV), which are different calculations entirely. It stops short of 5 only because the phrasing is dense enough that the two distinct computations it performs must be parsed out of one clause.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use statement, no prerequisites, and no named alternative. The reader can infer this is the tool for evaluating a cash-out offer against hedging, but nothing tells them when to prefer it over simulate_bonus_ev or when it is the wrong tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources