Skip to main content
Glama

Powerball and Mega Millions Winning Numbers MCP

Check a lottery ticket

lottery_check_ticket
Read-onlyIdempotent

Check a Powerball or Mega Millions ticket against the latest draw or a given draw date: which numbers matched, the prize tier, the prize amount (with Power Play, or with the multiplier printed on a Mega Millions ticket) and the odds of that tier. Optional Powerball Double Play matches.

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": {
      "game": "<game>",
      "numbers": "<numbers>",
      "special": "<special>"
    },
    "name": "lottery_check_ticket"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDraw date on the ticket, YYYY-MM-DD. Default the latest draw.
gameYespowerball or mega_millions.
numbersYesThe 5 white-ball numbers on the ticket.
specialYesThe Powerball (1-26) or Mega Ball (1-24) on the ticket.
multiplierNoMega Millions: the multiplier printed on the ticket (2, 3, 4, 5 or 10).
power_playNoPowerball: the ticket has Power Play.
double_playNoPowerball: also check the Double Play drawing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the description's added value is the computed-result surface: matches, prize tier, prize amount with multiplier handling, and tier odds. It does not mention failure modes such as an invalid ticket or a draw not yet published, which is the remaining transparency 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 front-loaded sentence with the scope stated first and the outputs listed after; it is dense but every clause carries relevant information. Slightly long-form for one sentence but no filler.

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?

There is no output schema, and the description accordingly enumerates the return contents (matches, tier, amount, odds, Double Play). For a 7-parameter tool with strong annotation coverage and a complete schema, the only missing piece is behavior on invalid input or unavailable draws.

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 the input schema already documents each parameter including game-specific notes for multiplier, power_play, and double_play. The description's phrase 'with Power Play, or with the multiplier printed on a Mega Millions ticket' links those flags to the prize-amount output, which is a small addition, but most parameter meaning is already in 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?

The description names a specific verb and resource ('Check a Powerball or Mega Millions ticket') and enumerates what it returns (matched numbers, prize tier, amount, odds), which cleanly separates it from the sibling lookup tools that only return drawings or frequencies.

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?

It implies the two usage modes — check against 'the latest draw or a given draw date' — and notes Double Play as optional, but it never states when not to use this tool or points to a sibling for raw number lookups. Usage is inferable rather than explicit.

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.