No user-submitted related servers found.
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.