APIVerve

Lottery Numbers

LotteryNumbers

Read-only

Lottery Numbers: Lottery Numbers fetches winning lottery numbers, bonus balls, draw dates, and jackpot amounts for major games. Specify Powerball, Mega Millions, EuroMillions, or Lotto Max to receive draw results with prize totals, and on paid plans the next draw's estimate and number frequency statistics from the last 100 draws. (Cost: 2 credits)

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": {
      "numbers": "<numbers>"
    },
    "name": "LotteryNumbers"
  }
}

Input Schema

Name	Required	Description
`date`	No	Optional date for historical lookup (YYYY-MM-DD). Returns the nearest draw to this date.
`stats`	No	Include number frequency statistics over the last 100 draws
`numbers`	Yes	The lottery game to lookup: powerball, megamillions, euromillions, or lottomax

Output Schema

Name	Required	Description
`data`	No
`error`	No	Error message, null on success
`status`	No	"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, non-destructive, open world), so the bar is lower. The description adds two genuinely useful behaviors not in the annotations: a fixed cost of 2 credits per call and plan-gated access to the next-draw estimate and 100-draw frequency statistics.

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, front-loaded with what is returned, then what to specify and what the paid tier adds, ending with the credit cost. It is dense but every clause carries information; the restated title prefix is the only minor waste.

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?

An output schema exists, so return-value explanation is not required, and the description still names the returned fields plus credit cost and plan gating. For a three-parameter read tool this is nearly complete, with only the date-lookup behavior left entirely to the schema.

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 the schema already defines all three parameters, and the baseline of 3 applies. The description only adds friendly display forms of the game names ('Mega Millions' vs the schema's 'megamillions'), and it does not mention the historical-date behavior that the date parameter enables.

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 uses a specific verb and resource ('fetches winning lottery numbers, bonus balls, draw dates, and jackpot amounts') and enumerates the supported games, so an agent can tell it apart from LotteryNumberGenerator. It stops short of naming that sibling explicitly, leaving the fetch-vs-generate distinction to be inferred from the word 'winning'.

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 usage by telling the caller to 'specify Powerball, Mega Millions, EuroMillions, or Lotto Max' and by noting that the next-draw estimate and frequency stats require a paid plan. There is no explicit statement of when to prefer this over the generator sibling or what happens outside paid plans, so guidance is contextual rather than directive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All APIVerve tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.