com.blocklottos/blocklottos
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_capabilitiesA | Read the authoritative Base game, 1-USDC price, gas, workflow, payout, and safety details. |
| get_jackpotA | Read the effective jackpot. Minimum: 100 USDC on Base or 100 POL on Polygon; higher live jackpot applies. |
| get_statsA | Read the current Base draw number, jackpot, next draw time, and contract metadata. |
| get_draw_historyA | Read one to ten completed Base draws, or begin at a specified public draw ID. |
| get_draw_proofA | Read the public proof for a Base draw. Omit draw_id for the current public proof when available. |
| get_wallet_ticketsB | Read a Base wallet's tickets for the active draw. This does not move funds. |
| check_wallet_prizesC | Check whether a Base wallet has an outstanding failed automatic prize payout. |
| get_or_create_referralA | Begin or finish secure shared affiliate enrollment. First call returns a message the EVM identity wallet must sign; resubmit its challenge_id and signature. The returned one-time management token protects EVM, Solana, and Cardano payout wallets and private balances. No funds move. |
| prepare_ticket_purchaseA | Prepare exactly one unsigned 1-USDC Base ticket purchase. It never signs or broadcasts. Obtain owner approval or apply a narrow owner policy before submitting returned wallet transactions. |
| confirm_ticket_purchaseB | Verify the Base receipt, sender, contract, method, and TicketPurchased event. This is the only completion check. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| agent_guide | Canonical machine-readable agent guide. |
| openapi | Canonical public OpenAPI document. |
TDQS
Scored across 10 tools
Most tools have clearly distinct actions and resources, especially the prepare/confirm purchase pair and the draw history/proof tools. The main overlap is between get_stats and get_jackpot, since get_stats also returns the current jackpot, and get_capabilities adds broader game metadata that could be confused with general stats reads.
All tool names use snake_case and follow a predictable action_object pattern, such as get_draw_history, prepare_ticket_purchase, and confirm_ticket_purchase. The few compound names like get_or_create_referral remain readable and consistent with the overall convention.
Ten tools is well scoped for a lottery ticket purchasing and wallet-checking server. The set separates discovery, read-only queries, referral setup, purchase preparation, and purchase confirmation without excessive tool proliferation.
Core flows are covered: reading game state, checking tickets and prizes, referral enrollment, and preparing/confirming a ticket purchase. However, there is a notable gap around prize resolution: check_wallet_prizes can detect an outstanding failed automatic payout, but no tool appears to retry, claim, or otherwise resolve that payout.