Lottery Number Skill

Overview

Generate multiple tickets at once with properly formatted number sets, perfect for lottery apps, gaming platforms, or random number generation needs.

Live Test Lottery Number Skill Skill →

The tool

Once your client is connected to the VerveKit server, this appears in its tool list as LotteryNumberSkill. It is read-only and open-world — it fetches and never mutates anything on your side — so most clients call it without asking you to confirm.

Tool call

{
  "name": "LotteryNumberSkill",
  "arguments": {}
}

Connecting

One server URL covers every skill in the catalog, including this one. Authorization is OAuth: the client opens a browser once, and there is no key to paste into a config file.

{
  "mcpServers": {
    "vervekit": {
      "url": "https://api.vervekit.com/v1/mcp"
    }
  }
}

Per-client setup — Claude, Cursor, VS Code, ChatGPT — is on the MCP setup page.

Arguments

These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made. Premium arguments are accepted on every plan but only take effect on plans that include them.

Argument	Type	Description
`game`Optional	string	Lottery game preset `custompowerballmegamillionseuromillionseurojackpotlotto649` default custom
`numbers`Optional	integer	Number of main numbers to pick (for custom game) default 6 · range 1–20
`max`Optional	integer	Maximum number for main numbers (for custom game) default 49 · range 10–100
`bonus`Optional	integer	Number of bonus numbers (for custom game) range 0–5
`tickets`Optional	integer	Number of tickets to generate default 1 · range 1–25
`bonusmax`Optional	integer	Highest value a bonus ball can take. Only applies when game is custom; named games use their own rules default 10 · range 1–∞

What the model gets back

The result carries a structuredContent object matching the tool's declared outputSchema, so a client reads fields without parsing prose. status is "ok" and error is null on success; a null field means the value was not available for that input, not that the call failed.

Result

{
  "status": "ok",
  "error": null,
  "data": {
    "game": "Powerball (US)",
    "game_type": "powerball",
    "config": {
      "main_numbers_count": 5,
      "main_numbers_range": "1-69",
      "bonus_numbers_count": 1,
      "bonus_numbers_range": "1-26"
    },
    "tickets_generated": 3,
    "tickets": [
      {
        "ticket_number": 1,
        "main_numbers": [
          11,
          12,
          51,
          53,
          58
        ],
        "bonus_numbers": [
          3
        ]
      },
      {
        "ticket_number": 2,
        "main_numbers": [
          4,
          24,
          28,
          46,
          61
        ],
        "bonus_numbers": [
          3
        ]
      },
      {
        "ticket_number": 3,
        "main_numbers": [
          12,
          13,
          29,
          49,
          60
        ],
        "bonus_numbers": [
          6
        ]
      }
    ]
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Field	Type	Example	Description
`game`	string	`Powerball (US)`	Lottery game type used for generation
`game_type`	string	`powerball`	The lottery game the numbers were picked for
`config`	object	`{…}`	The game's rules, showing how many numbers are drawn from what range
`config.main_numbers_count`	number	`5`	How many main numbers the game draws
`config.main_numbers_range`	string	`1-69`	Range the main numbers are drawn from
`config.bonus_numbers_count`	number	`1`	How many bonus numbers the game draws
`config.bonus_numbers_range`	string	`1-26`	Range the bonus numbers are drawn from
`tickets_generated`	number	`3`	Number of tickets returned
`tickets`	array[3]		Array of generated lottery tickets with numbers
`tickets.0.ticket_number`	number	`1`	Position of this ticket in the set
`tickets.0.main_numbers`	array	`[11,12,51]`	Main lottery numbers for the ticket
`tickets.0.bonus_numbers`	array	`[3]`	Bonus numbers for the ticket if applicable

Failure modes

Errors come back as tool errors carrying a sentence the model can act on, not a bare status code. Error handling covers the full list.

Status	What it means
`400` / `422`	The arguments did not validate. The message names the offending one.
`401`	The OAuth session is invalid or expired — reconnect the server.
`403`	Blocked by a key restriction or an IP allow-list. Never a bad identity.
`404`	This skill is not part of VerveKit. Check the catalog.
`429`	Out of credits, or a brief rate limit. The message tells them apart.

A call costs 2 credits each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.

Use cases

Lottery Apps: Build lottery number picker apps with support for popular games like Powerball, Mega Millions, and international lotteries
Quick Pick Numbers: Generate quick pick numbers for lottery games with customizable number ranges and bonus ball configurations
Gaming Systems: Create random number sets for gaming applications, contests, and raffle systems with verifiable randomization
International Support: Support multiple international lottery formats including EuroMillions, UK Lotto, and regional lottery games worldwide

Other ways to use Lottery Number Skill

Set up Lottery Number Skill on VerveKit, or reach the same source a different way. Your VerveKit account and credits work on all of them — one key, one balance.

Call it as a REST APIOne HTTPS endpoint and an x-api-key header, with SDKs for Node, Python and .NET.APIVerve →Reference →