Skip to main content
Glama

Powerball and Mega Millions Winning Numbers MCP

Latest Powerball and Mega Millions numbers

lottery_latest_numbers
Read-onlyIdempotent

The latest Powerball and Mega Millions winning numbers: five white balls, the Powerball or Mega Ball, the Power Play multiplier and Double Play numbers, plus the next draw date. Optionally the last 2 to 10 draws. Results usually reach the feed the morning after the draw.

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

Input Schema

NameRequiredDescriptionDefault
gameNopowerball, mega_millions or both (default both).
drawsNoHow many recent draws per game, 1 to 10. Default 1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: the exact payload shape (white balls, multiplier, Double Play, next draw date) and, importantly, data freshness ('Results usually reach the feed the morning after the draw'), which tells the agent when a missing result is expected rather than an error.

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?

Two sentences, both front-loaded: the payload contents come first and the freshness caveat last. The list of returned fields is dense but each item is informative; only the '2 to 10' phrasing is wasted ambiguity against the schema's 1-to-10 range.

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?

With no output schema, the description carries the burden of describing return values and does so thoroughly, including an unusual field (Double Play) an agent would not otherwise anticipate. The only shortfall is the absent guidance on distinguishing this from sibling tools and the minor draws-range mismatch.

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 both parameters (game enum and draws) are already fully documented, making 3 the baseline. The description does mention the optional multi-draw mode, but its wording 'the last 2 to 10 draws' is narrower than the schema's stated minimum of 1 and adds no syntax or format detail 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 the specific resource (latest Powerball and Mega Millions winning numbers) and enumerates the components returned: five white balls, the Powerball/Mega Ball, Power Play multiplier, Double Play numbers and next draw date. That is a concrete verb-plus-resource statement an agent can match to a request, though it never explicitly contrasts itself with siblings like lottery_numbers_by_date or lottery_number_frequency.

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: the phrase 'Optionally the last 2 to 10 draws' signals that the tool also serves short historical windows, but there is no statement of when to pick this over lottery_numbers_by_date for older dates or lottery_check_ticket for verification. No prerequisites or exclusions are given, so the agent must infer routing from sibling names alone.

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.