Skip to main content
Glama
Sign In

Lottery Numbers

by com.intoperson.tools
OverviewDiscussionsAdmin
This connector has been deprecated

This service has been retired and the endpoint is no longer available.

Numbers from the user's own sentence (a link)

sentence_numbers_link

For a user who wants lottery numbers drawn from a sentence of their own (a wish, a name, a question). If they also give numbers to keep or leave out, a date, or an odd/sum wish, call pick_numbers with all of it instead (the sentence as text). Give the sentence and the lottery format (a game, or custom count and max with optional extras); the answer is one link. For a game it opens drawstoday.com with the sentence filled in, and the numbers are drawn when the user presses send there; for a custom format it is a prismtect.com link that draws them there (it works for 30 days). This tool makes no numbers. Ranges: min 0 or 1, max up to 99, at most 8 numbers in all.

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": {
      "text": "<text>"
    },
    "name": "sentence_numbers_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNocustom: the largest number.
minNocustom: the smallest number, 0 or 1.
gameNoA game, or "custom" with count and max. May be left out when count and max are given.
textYesThe user's sentence, 1 to 500 characters, no line breaks.
countNocustom: how many numbers.
extra_maxNocustom: the largest extra number (extras start at 1).
extra_countNocustom: how many extra (bonus) numbers, drawn apart.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / game / enum
      Previous value: -[
-  "kr645",
-  "powerball",
-  "megamillions",
-  "euromillions",
-  "uk_lotto",
-  "jp_loto6",
-  "jp_loto7",
-  "thunderball",
-  "set_for_life",
-  "fr_loto",
-  "br_megasena",
-  "br_lotofacil",
-  "br_quina",
-  "br_maismilionaria",
-  "custom"
-]New value: +[
+  "kr645",
+  "powerball",
+  "megamillions",
+  "euromillions",
+  "uk_lotto",
+  "jp_loto6",
+  "jp_loto7",
+  "thunderball",
+  "set_for_life",
+  "fr_loto",
+  "br_megasena",
+  "br_quina",
+  "br_maismilionaria",
+  "custom"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / game / enum
      Previous value: -[
-  "kr645",
-  "powerball",
-  "megamillions",
-  "euromillions",
-  "uk_lotto",
-  "jp_loto6",
-  "jp_loto7",
-  "custom"
-]New value: +[
+  "kr645",
+  "powerball",
+  "megamillions",
+  "euromillions",
+  "uk_lotto",
+  "jp_loto6",
+  "jp_loto7",
+  "thunderball",
+  "set_for_life",
+  "fr_loto",
+  "br_megasena",
+  "br_lotofacil",
+  "br_quina",
+  "br_maismilionaria",
+  "custom"
+]
  3. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already indicate a non-read-only, open-world, non-idempotent operation, and the description adds substantial context beyond them: the tool returns one link, game links open drawstoday.com and draw only when the user presses send there, custom links use prismtect.com and work for 30 days. It also clarifies that the tool itself makes no numbers and gives operating ranges.

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?

The description is front-loaded with the user intent and then covers alternatives, inputs, return behavior, and limits. Despite being longer than a simple tool description, every sentence carries necessary routing or behavioral information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a seven-parameter tool with no output schema, the description is complete enough to call correctly: it explains the input format, the return value, the external-site behavior, the 30-day validity, and the numerical limits. Nothing essential for correct invocation is missing.

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 documents all seven parameters thoroughly. The description reiterates the main choice between a named game and custom count/max with optional extras, but adds only limited meaning beyond the structured fields.

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 states a specific outcome: it returns a link that draws lottery numbers from the user's sentence. It also explicitly distinguishes this from pick_numbers when extra constraints are involved, so an agent can select it without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly defines when to use this tool and names the alternative: if the user supplies numbers to keep or leave out, a date, or an odd/sum wish, call pick_numbers instead with the sentence as text. That is an explicit routing rule rather than implied usage.

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

All Lottery Numbers toolsInspect
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.

Resources