Skip to main content
Glama

GambleMath — Casino RTP, Bonus EV & UKGC Register Lab

simulate_bonus_ev

Calculate closed-form Cash EV ($) and completion probability (%) for a casino deposit bonus.

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

Input Schema

NameRequiredDescriptionDefault
bonusUsdNo
wageringXNo
depositUsdNo
slotRtpPctNo
includeDepositInWagerNo

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?

With no annotations, the description carries the full burden, yet it discloses little: no statement of model assumptions behind 'closed-form', no permission or rate-limit context, and no note on how the two outputs relate or what happens with missing inputs. The word 'closed-form' hints at an analytical approximation but the implication is never spelled out.

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 zero filler and the two output metrics stated up front. Its brevity is efficient, though it edges toward under-specification rather than being genuinely complete.

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?

For a five-parameter calculation tool with no annotations and no output schema, the description is thin. It does name the two return values, which is helpful, but leaves the entire input contract and the calculation's assumptions undocumented.

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?

Five parameters with 0% schema description coverage, and the description mentions none of them. Parameter names (wageringX, slotRtpPct, includeDepositInWager) are suggestive but the description adds no meaning about units, expected ranges, defaults, or which are required for a meaningful result.

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?

States a specific verb ('Calculate') and two concrete outputs (Cash EV in $, completion probability in %) scoped to a casino deposit bonus, which is clearly distinct from the sibling audit/lookup tools. It stops short of explicitly contrasting itself with those siblings, so a 4 rather than a 5.

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?

The description gives no when-to-use conditions, no prerequisites, and no mention of alternatives such as audit_slot_rtp or audit_parlay_and_cashout. An agent must infer from the name alone whether this is the right tool for a given scenario.

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