Skip to main content
Glama

Powerball and Mega Millions Winning Numbers MCP

Lottery numbers by date

lottery_numbers_by_date
Read-onlyIdempotent

Powerball or Mega Millions winning numbers for a draw date, or every draw between two dates (up to 400 days). When no draw was held on the date, returns the draws just before and after. Powerball back to 2010, Mega Millions back to 2002.

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_numbers_by_date"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoRange end, YYYY-MM-DD. Default today.
dateNoOne draw date, YYYY-MM-DD.
gameYespowerball or mega_millions.
startNoRange start, YYYY-MM-DD. Default 30 days before end.

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 cover the safety profile (readOnly, idempotent, non-destructive, openWorld), but the description adds real context: a 400-day cap on ranges, fallback behavior returning the nearest draws when no draw occurred, and the earliest available data per game. These are behavioral details an agent could not derive from the schema or annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact sentences, front-loaded with the primary capability, followed by the fallback rule and then data coverage. No filler, and each sentence carries distinct information.

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?

For a four-parameter read-only lookup with no output schema, the definition supplies the key edges: supported date bounds, range cap, and no-draw fallback. It does not sketch the return payload (e.g., the winning number fields), which is a minor residual gap given the read-only, predictable nature of the result.

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, but the description adds a constraint not present in the schema: the start/end range is capped at 400 days. That meaningfully informs how the caller should set start and end, particularly since the schema only mentions defaults.

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 a specific resource (Powerball or Mega Millions winning numbers) and distinguishes two modes: a single draw date versus a range of draws. It stops short of identifying which sibling tool to use for adjacent needs such as latest numbers or frequency, so an agent must infer the boundary itself.

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 two-mode framing (single date vs date range) and the historical coverage note, which helps an agent know whether a date is queryable at all. However, there is no explicit when-not-to-use statement and no comparison to lottery_latest_numbers, lottery_check_ticket, or lottery_number_frequency.

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.