mcp-server-taiwan-lottery
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| latest_drawA | Latest official draw of a Taiwan Lottery (台灣彩券) game: period, date, winning numbers in ascending and in draw order, the special number (大樂透 特別號) or second-zone number (威力彩 第二區) where the game has one, the digits for 3星彩/4星彩, the super number for 賓果賓果, and the prize table published for that draw (tier, winners, NTD per winning ticket). Data comes from the official Taiwan Lottery API (api.taiwanlottery.com). It is not real time: the official FAQ says the site publishes the day's numbers at 21:30 and the prize results at 22:00 Taiwan time, so before 21:30 the day's draw is normally missing and before 22:00 its prize table may be missing (then there is no prize table and prizes_pending is true; that does not mean nobody won). Never fill in numbers the API does not have. Official announcements prevail. Every result has |
| get_drawA | One official draw, by period number or by date (YYYY-MM-DD, Taiwan time). Returns the same fields as latest_draw. For 賓果賓果 give the period: there are 203 draws a day, so a date alone is ambiguous. If there was no draw that day the error says which days the game is drawn. Data comes from the official Taiwan Lottery API (api.taiwanlottery.com). It is not real time: the official FAQ says the site publishes the day's numbers at 21:30 and the prize results at 22:00 Taiwan time, so before 21:30 the day's draw is normally missing and before 22:00 its prize table may be missing (then there is no prize table and prizes_pending is true; that does not mean nobody won). Never fill in numbers the API does not have. Official announcements prevail. Every result has |
| list_drawsA | Official draws of one game: one month (month: YYYY-MM) or the newest N draws (last_n, 1-100, default 10). For 賓果賓果 use date (YYYY-MM-DD) or last_n. Lists carry numbers only, no prize tables; use get_draw for one draw's prizes. Data comes from the official Taiwan Lottery API (api.taiwanlottery.com). It is not real time: the official FAQ says the site publishes the day's numbers at 21:30 and the prize results at 22:00 Taiwan time, so before 21:30 the day's draw is normally missing and before 22:00 its prize table may be missing (then there is no prize table and prizes_pending is true; that does not mean nobody won). Never fill in numbers the API does not have. Official announcements prevail. Every result has |
| check_ticketA | Check a ticket against an official draw (default: the newest draw in the official data; pass period for another draw). Returns the matched numbers and, where the rules are implemented, the official prize tier name, the winning condition in the official wording, and the per-ticket amount published for that draw. Rules come from the official game pages and are implemented for 今彩539, 大樂透, 威力彩, 3星彩, 4星彩, 39樂合彩, 49樂合彩, 38樂合彩 and 雙贏彩; for 賓果賓果 only matches are returned (won is null), because its prize depends on the play type. Ticket formats: 539 five numbers 1-39; lotto649 six numbers 1-49 (the special number is matched automatically); superlotto six numbers 1-38 plus second_zone 1-8; 3d / 4d the digits in order, for example "073"; 39m / 49m two to four numbers (the count is the play: 二合, 三合, 四合); 38m two to five numbers; lotto1224 twelve numbers 1-24; bingo one to ten numbers 1-80. One ticket line per call. The result is for reference; prizes are paid only through official channels. Data comes from the official Taiwan Lottery API (api.taiwanlottery.com). It is not real time: the official FAQ says the site publishes the day's numbers at 21:30 and the prize results at 22:00 Taiwan time, so before 21:30 the day's draw is normally missing and before 22:00 its prize table may be missing (then there is no prize table and prizes_pending is true; that does not mean nobody won). Never fill in numbers the API does not have. Official announcements prevail. Every result has |
| number_statsA | Historical frequency of each number over the newest N official draws (last_n 1-200, default 30): count per number, draws since each number was last seen, and the most and least frequent numbers in that window (often called hot and cold numbers). These are counts of past draws only. Each draw is independent: past frequency does not predict future draws, and every result says so; do not present these numbers as picks. 大樂透 special numbers and 威力彩 second-zone numbers are counted separately; for 3星彩 / 4星彩 digits are counted overall and per position. Data comes from the official Taiwan Lottery API (api.taiwanlottery.com). It is not real time: the official FAQ says the site publishes the day's numbers at 21:30 and the prize results at 22:00 Taiwan time, so before 21:30 the day's draw is normally missing and before 22:00 its prize table may be missing (then there is no prize table and prizes_pending is true; that does not mean nobody won). Never fill in numbers the API does not have. Official announcements prevail. Every result has |
| draw_scheduleA | Draw days and time from the official schedule (今彩539, 3星彩, 4星彩, 39樂合彩: Monday to Saturday; 大樂透 and 49樂合彩: Tuesday and Friday; 威力彩: Monday and Thursday; all at 20:30 Taiwan time; 賓果賓果 every 5 minutes 07:05-23:55, every day), the next draw date from the official API, official schedule notices if any, and when the official site publishes results. Data comes from the official Taiwan Lottery API (api.taiwanlottery.com). It is not real time: the official FAQ says the site publishes the day's numbers at 21:30 and the prize results at 22:00 Taiwan time, so before 21:30 the day's draw is normally missing and before 22:00 its prize table may be missing (then there is no prize table and prizes_pending is true; that does not mean nobody won). Never fill in numbers the API does not have. Official announcements prevail. Every result has |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
latest_draw, get_draw, and list_draws all return draw data and could be momentarily confused, but descriptions make the boundaries clear (newest single, specific single by period/date, and multi-draw listing without prize tables). check_ticket, number_stats, and draw_schedule are clearly distinct.
Most tools follow a verb_noun pattern (get_draw, list_draws, check_ticket), with a few noun-phrase outliers (latest_draw, number_stats, draw_schedule). All are snake_case and readable, so the deviation is minor.
Six tools is well-scoped for a lottery data server: each covers a distinct need (latest, single, list, ticket check, stats, schedule) with no filler.
Core lifecycle is covered: latest/current draws, historical listing, single-draw prize tables, ticket validation across games, frequency stats, and schedule. A minor gap is the lack of a tool to enumerate supported games or fetch game rules directly.