lottery-mcp
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_super_lotto_monthB | Get lottery, super lotto 638 (威力彩), data in the specified month Args: year: target year, e.g. 2024 month: target month, e.g. 5 |
| get_lotto_649_monthC | Get lottery, super lotto 649 (大樂透), data in the specified month Args: year: target year, e.g. 2024 month: target month, e.g. 5 |
| get_daily_cash_monthB | Get lottery, daily cash (今彩539), data in the specified month Args: year: target year, e.g. 2024 month: target month, e.g. 5 |
| get_lotto_4d_monthC | Get lottery, lotto 4d (4星彩), data in the specified month Args: year: target year, e.g. 2024 month: target month, e.g. 5 |
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 4 tools
Each tool targets a distinct lottery game (super lotto 638, lotto 649, daily cash, lotto 4d) with no overlap. The game name in the tool name and description makes the purpose unambiguous.
All four tools follow a consistent get_<game>_month pattern. The naming is predictable and clearly indicates the action and resource.
Four tools is reasonable given the server covers four distinct lottery games. The scope is narrow but well-defined, and each tool earns its place.
The surface only provides monthly data retrieval for each game. There are no tools for fetching individual draws, latest results, or time ranges, which are common needs. CRUD operations are not applicable, but the read-only surface is limited to a single granularity.