Skip to main content
Glama

Thunderball number generator

hopi_thunderball_generator
Read-onlyIdempotent

Generate random UK Thunderball lines. Each line has 5 main numbers from 1 to 39 (unique, sorted low to high) plus one Thunderball from 1 to 14, drawn with cryptographic randomness. Draws are Tuesday, Wednesday, Friday and Saturday; the fixed top prize is £500,000 at odds of 1 in 8,060,598. Source: https://hopi.co.uk/thunderball-generator/

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

Input Schema

NameRequiredDescriptionDefault
linesNoHow many lines to generate, 1 to 10 (default 1)

Output Schema

NameRequiredDescriptionDefault
gameNo
linesNo
summaryYes
source_urlYesThe tool's page on hopi.co.uk (cite or open to check the figure)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "game": {
      +      "type": "string"
      +    },
      +    "lines": {
      +      "type": "array"
      +    },
      +    "source_url": {
      +      "description": "The tool's page on hopi.co.uk (cite or open to check the figure)",
      +      "type": "string"
      +    },
      +    "summary": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "source_url",
      +    "summary"
      +  ],
      +  "type": "object"
      +}
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/non-destructive/openWorld=false, so the safety burden is light. The description still adds real behavioural value: it discloses that randomness is cryptographic (not pseudo-random), specifies uniqueness and sorting guarantees for the output set, and gives the source URL. The prize odds and draw-day trivia add little for invocation, and the 'cryptographic randomness' claim sits in mild tension with idempotentHint=true (repeated calls yield different lines), though that hint refers to environment effects rather than identical output.

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

Conciseness3/5

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

The core specification is front-loaded in a clean first sentence. The second sentence, however, spends most of its length on lottery trivia (draw days, £500,000 top prize, 1 in 8,060,598 odds) and a source URL that do not help an agent decide or invoke – material that could be trimmed without loss.

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 an output schema present and a single fully documented optional parameter, the description needs only to define the generation rules and it does so precisely (ranges, uniqueness, sorting, randomness source). Nothing required for correct invocation is missing; the omission of any mention of the 'lines' parameter is covered by 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?

The single 'lines' parameter has 100% schema description coverage including default and 1-10 bounds, so the schema carries the semantics. The description never mentions the lines parameter, so it adds nothing beyond structured data; baseline 3 applies.

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?

States a specific verb and resource ('Generate random UK Thunderball lines') and immediately defines the exact output format: 5 unique main numbers 1-39 sorted low to high plus one Thunderball 1-14. This unambiguously separates it from hopi_euromillions_generator, hopi_lottery_number_generator and hopi_random_number_generator without opening any schema.

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 by the name of the game – an agent can infer it is the tool to call for Thunderball lines, but there is no explicit statement of when to use it and no mention of the sibling generators (Euromillions, Set For Life, generic lottery) that could be confused with it. Draw days are mentioned but only as trivia, not as a usage condition.

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.

Resources