k-lottery
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOTTO_TIMEOUT | No | HTTP request timeout in seconds | 10 |
| LOTTO_USER_ID | Yes | Your DHLottery account ID (required) | |
| LOTTO_DATA_DIR | No | Directory to store cookies and history | ./data |
| LOTTO_PASSWORD | Yes | Your DHLottery account password (required) | |
| LOTTO_USER_AGENT | No | User-Agent header | Chrome |
| KLOTTERY_MCP_ALLOW_BUY | No | Set to '1' to expose lotto_buy tool (default: not exposed) | |
| LOTTO_REQUEST_INTERVAL | No | Minimum interval between consecutive requests in seconds | 0.3 |
| KLOTTERY_MCP_ALLOW_DEPOSIT | No | Set to '1' to expose lotto_deposit tool (default: not exposed) |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lotto_statusA | 예치금 잔액·구매 한도·건전구매 서약 유효성을 조회한다. |
| lotto_resultsA | 구매 내역과 당첨 결과를 조회한다. 등수는 서버가 계산한 값이다.
|
| lotto_drawA | 공개 추첨 결과를 조회한다. 로그인이 필요 없다. |
| lotto_buy_precheckA | 구매 사전 점검 (드라이런). 게이트 판정과 다음 단계만 알려주고 절대 구매하지 않는다. 회차당 한도가 남아 있으면 이미 구매한 회차라도 남은 만큼 더 살 수 있다.
남은 게임 수는 |
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 has a clearly distinct purpose: status checks account-level limits, results retrieves personal purchase history and winnings, draw fetches public draw outcomes, and buy_precheck performs a dry-run gate check. There is no overlap between these four tools.
All tool names share the 'lotto_' prefix, creating a consistent namespace. The second part varies between nouns (status, results, draw) and a compound action (buy_precheck), but the pattern is still predictable and readable.
With exactly 4 tools, the server is well-scoped and each tool serves a distinct function. There are no redundant or superfluous tools, and the count is within the ideal range for a focused utility.
The tool set covers the core read-only and pre-check operations relevant to a lottery assistant: status, personal results, public draws, and purchase pre-flight. A actual purchase or cancellation tool is absent, but that appears intentional given the server's pre-check focus, so no major gaps block the intended workflow.