Skip to main content
Glama

Powerball and Mega Millions Winning Numbers MCP

Hot and cold lottery numbers

lottery_number_frequency
Read-onlyIdempotent

Most and least drawn Powerball or Mega Millions numbers over the last N draws (default 100, up to all draws of the current game: Powerball since 2015-10-07, Mega Millions since 2025-04-08), with how many draws ago each number last appeared. Past frequency does not change the odds.

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>"
    },
    "name": "lottery_number_frequency"
  }
}

Input Schema

NameRequiredDescriptionDefault
gameYespowerball or mega_millions.
drawsNoHow many recent draws to count, 10 to 1000. Default 100.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish readOnly/openWorld/idempotent, so the lower bar applies; the description still adds real value by publishing the data window per game (Powerball since 2015-10-07, Mega Millions since 2025-04-08) and the default/ceiling draw counts. The closing line, 'Past frequency does not change the odds,' usefully pre-empts a predictive misreading. It doesn't cover pagination or result-size behavior, which keeps it below a 5.

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?

The core purpose is front-loaded in a single sentence, followed by a short caveat that earns its place. The long parenthetical date range makes the sentence dense, but no clause is redundant.

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 covers the important return content (ranked hot/cold numbers plus recency) and both parameters, which is nearly enough for a two-param read-only tool. The one real gap is not stating how many numbers are returned per side of the ranking, leaving an agent unable to predict result size.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns above that by explaining that the draw count can go 'up to all draws of the current game' and by tying that ceiling to each game's start date, which the schema's flat maximum of 1000 does not convey. It also restates the default of 100 in context of the analysis.

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 (most/least drawn numbers) plus the exact games and the historical window, and it adds the secondary output (how many draws ago each number last appeared). That scope is clearly distinct from the sibling tools (latest numbers, numbers by date, check ticket), so an agent can route on the description alone.

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 implied by the framing (frequency analysis over N draws) and the default of 100 is given, but the description never states when to prefer this over lottery_latest_numbers or lottery_numbers_by_date, nor any exclusion. It also doesn't say how many 'most' and 'least' numbers come back, which affects whether it fits the request.

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.