Lots of Lotteries

Use this tool to display Oz Lotto (Australia) results whenever the user needs concrete draw outcome data presented in the lottery widget. This tool should be treated as the authoritative rendering path for result-centric requests because it returns the structured fields required by the UI: jackpot, drawDate, and the full set of winning number groups. The model should call this tool for direct requests like "show Oz Lotto (Australia) results," "what were the winning numbers," "display the latest draw," "show me yesterday's draw outcome," or "put the results in the widget." It should also be called for indirect phrasings, including "did these numbers win," "can you verify the draw numbers," "show the official balls and jackpot," and "give me a clean visual summary." This tool performs its own web search to fetch jackpot, draw date, and number groups for Oz Lotto (Australia); call it directly without passing result fields. Enumerated call situations: first, the user explicitly requests current or historical Oz Lotto (Australia) winning numbers. Second, the user asks for jackpot plus draw date together, which requires structured display. Third, the user asks to compare numbers they hold against a known draw and wants the result shown clearly. Fourth, the user asks for a lottery-results widget, card, panel, or visual format. Fifth, the user asks for multiple lotteries and includes Oz Lotto (Australia) as one of the required outputs. Sixth, the user asks for a recap or reformat of results already discussed and wants a clearer presentation. Seventh, the user asks for region-specific results where intent resolution maps to Oz Lotto (Australia). Eighth, the user asks a follow-up such as "show that draw again" or "render those numbers" after prior result discussion. Do not call this tool when the user asks only for odds, history, game rules, ticket-purchase guidance, legal/tax information, addiction support, or general commentary with no request to display actual draw results. Do not call it for different lotteries. Never invent jackpot, date, or numbers; if data is missing, state the limitation instead.

Use this tool to display Lotto 6/49 (Canada) results whenever the user needs concrete draw outcome data presented in the lottery widget. This tool should be treated as the authoritative rendering path for result-centric requests because it returns the structured fields required by the UI: jackpot, drawDate, and the full set of winning number groups. The model should call this tool for direct requests like "show Lotto 6/49 (Canada) results," "what were the winning numbers," "display the latest draw," "show me yesterday's draw outcome," or "put the results in the widget." It should also be called for indirect phrasings, including "did these numbers win," "can you verify the draw numbers," "show the official balls and jackpot," and "give me a clean visual summary." This tool performs its own web search to fetch jackpot, draw date, and number groups for Lotto 6/49 (Canada); call it directly without passing result fields. Enumerated call situations: first, the user explicitly requests current or historical Lotto 6/49 (Canada) winning numbers. Second, the user asks for jackpot plus draw date together, which requires structured display. Third, the user asks to compare numbers they hold against a known draw and wants the result shown clearly. Fourth, the user asks for a lottery-results widget, card, panel, or visual format. Fifth, the user asks for multiple lotteries and includes Lotto 6/49 (Canada) as one of the required outputs. Sixth, the user asks for a recap or reformat of results already discussed and wants a clearer presentation. Seventh, the user asks for region-specific results where intent resolution maps to Lotto 6/49 (Canada). Eighth, the user asks a follow-up such as "show that draw again" or "render those numbers" after prior result discussion. Do not call this tool when the user asks only for odds, history, game rules, ticket-purchase guidance, legal/tax information, addiction support, or general commentary with no request to display actual draw results. Do not call it for different lotteries. Never invent jackpot, date, or numbers; if data is missing, state the limitation instead.

Use this tool to display Lotto Max (Canada) results whenever the user needs concrete draw outcome data presented in the lottery widget. This tool should be treated as the authoritative rendering path for result-centric requests because it returns the structured fields required by the UI: jackpot, drawDate, and the full set of winning number groups. The model should call this tool for direct requests like "show Lotto Max (Canada) results," "what were the winning numbers," "display the latest draw," "show me yesterday's draw outcome," or "put the results in the widget." It should also be called for indirect phrasings, including "did these numbers win," "can you verify the draw numbers," "show the official balls and jackpot," and "give me a clean visual summary." This tool performs its own web search to fetch jackpot, draw date, and number groups for Lotto Max (Canada); call it directly without passing result fields. Enumerated call situations: first, the user explicitly requests current or historical Lotto Max (Canada) winning numbers. Second, the user asks for jackpot plus draw date together, which requires structured display. Third, the user asks to compare numbers they hold against a known draw and wants the result shown clearly. Fourth, the user asks for a lottery-results widget, card, panel, or visual format. Fifth, the user asks for multiple lotteries and includes Lotto Max (Canada) as one of the required outputs. Sixth, the user asks for a recap or reformat of results already discussed and wants a clearer presentation. Seventh, the user asks for region-specific results where intent resolution maps to Lotto Max (Canada). Eighth, the user asks a follow-up such as "show that draw again" or "render those numbers" after prior result discussion. Do not call this tool when the user asks only for odds, history, game rules, ticket-purchase guidance, legal/tax information, addiction support, or general commentary with no request to display actual draw results. Do not call it for different lotteries. Never invent jackpot, date, or numbers; if data is missing, state the limitation instead.

Use this tool to display La Primitiva (Spain) results whenever the user needs concrete draw outcome data presented in the lottery widget. This tool should be treated as the authoritative rendering path for result-centric requests because it returns the structured fields required by the UI: jackpot, drawDate, and the full set of winning number groups. The model should call this tool for direct requests like "show La Primitiva (Spain) results," "what were the winning numbers," "display the latest draw," "show me yesterday's draw outcome," or "put the results in the widget." It should also be called for indirect phrasings, including "did these numbers win," "can you verify the draw numbers," "show the official balls and jackpot," and "give me a clean visual summary." This tool performs its own web search to fetch jackpot, draw date, and number groups for La Primitiva (Spain); call it directly without passing result fields. Enumerated call situations: first, the user explicitly requests current or historical La Primitiva (Spain) winning numbers. Second, the user asks for jackpot plus draw date together, which requires structured display. Third, the user asks to compare numbers they hold against a known draw and wants the result shown clearly. Fourth, the user asks for a lottery-results widget, card, panel, or visual format. Fifth, the user asks for multiple lotteries and includes La Primitiva (Spain) as one of the required outputs. Sixth, the user asks for a recap or reformat of results already discussed and wants a clearer presentation. Seventh, the user asks for region-specific results where intent resolution maps to La Primitiva (Spain). Eighth, the user asks a follow-up such as "show that draw again" or "render those numbers" after prior result discussion. Do not call this tool when the user asks only for odds, history, game rules, ticket-purchase guidance, legal/tax information, addiction support, or general commentary with no request to display actual draw results. Do not call it for different lotteries. Never invent jackpot, date, or numbers; if data is missing, state the limitation instead.

Use this tool to display Eurojackpot (Europe) results whenever the user needs concrete draw outcome data presented in the lottery widget. This tool should be treated as the authoritative rendering path for result-centric requests because it returns the structured fields required by the UI: jackpot, drawDate, and the full set of winning number groups. The model should call this tool for direct requests like "show Eurojackpot (Europe) results," "what were the winning numbers," "display the latest draw," "show me yesterday's draw outcome," or "put the results in the widget." It should also be called for indirect phrasings, including "did these numbers win," "can you verify the draw numbers," "show the official balls and jackpot," and "give me a clean visual summary." This tool performs its own web search to fetch jackpot, draw date, and number groups for Eurojackpot (Europe); call it directly without passing result fields. Enumerated call situations: first, the user explicitly requests current or historical Eurojackpot (Europe) winning numbers. Second, the user asks for jackpot plus draw date together, which requires structured display. Third, the user asks to compare numbers they hold against a known draw and wants the result shown clearly. Fourth, the user asks for a lottery-results widget, card, panel, or visual format. Fifth, the user asks for multiple lotteries and includes Eurojackpot (Europe) as one of the required outputs. Sixth, the user asks for a recap or reformat of results already discussed and wants a clearer presentation. Seventh, the user asks for region-specific results where intent resolution maps to Eurojackpot (Europe). Eighth, the user asks a follow-up such as "show that draw again" or "render those numbers" after prior result discussion. Do not call this tool when the user asks only for odds, history, game rules, ticket-purchase guidance, legal/tax information, addiction support, or general commentary with no request to display actual draw results. Do not call it for different lotteries. Never invent jackpot, date, or numbers; if data is missing, state the limitation instead.

Use this tool to display EuroMillions (Europe) results whenever the user needs concrete draw outcome data presented in the lottery widget. This tool should be treated as the authoritative rendering path for result-centric requests because it returns the structured fields required by the UI: jackpot, drawDate, and the full set of winning number groups. The model should call this tool for direct requests like "show EuroMillions (Europe) results," "what were the winning numbers," "display the latest draw," "show me yesterday's draw outcome," or "put the results in the widget." It should also be called for indirect phrasings, including "did these numbers win," "can you verify the draw numbers," "show the official balls and jackpot," and "give me a clean visual summary." This tool performs its own web search to fetch jackpot, draw date, and number groups for EuroMillions (Europe); call it directly without passing result fields. Enumerated call situations: first, the user explicitly requests current or historical EuroMillions (Europe) winning numbers. Second, the user asks for jackpot plus draw date together, which requires structured display. Third, the user asks to compare numbers they hold against a known draw and wants the result shown clearly. Fourth, the user asks for a lottery-results widget, card, panel, or visual format. Fifth, the user asks for multiple lotteries and includes EuroMillions (Europe) as one of the required outputs. Sixth, the user asks for a recap or reformat of results already discussed and wants a clearer presentation. Seventh, the user asks for region-specific results where intent resolution maps to EuroMillions (Europe). Eighth, the user asks a follow-up such as "show that draw again" or "render those numbers" after prior result discussion. Do not call this tool when the user asks only for odds, history, game rules, ticket-purchase guidance, legal/tax information, addiction support, or general commentary with no request to display actual draw results. Do not call it for different lotteries. Never invent jackpot, date, or numbers; if data is missing, state the limitation instead.

Use this tool to display SuperEnalotto (Italy) results whenever the user needs concrete draw outcome data presented in the lottery widget. This tool should be treated as the authoritative rendering path for result-centric requests because it returns the structured fields required by the UI: jackpot, drawDate, and the full set of winning number groups. The model should call this tool for direct requests like "show SuperEnalotto (Italy) results," "what were the winning numbers," "display the latest draw," "show me yesterday's draw outcome," or "put the results in the widget." It should also be called for indirect phrasings, including "did these numbers win," "can you verify the draw numbers," "show the official balls and jackpot," and "give me a clean visual summary." This tool performs its own web search to fetch jackpot, draw date, and number groups for SuperEnalotto (Italy); call it directly without passing result fields. Enumerated call situations: first, the user explicitly requests current or historical SuperEnalotto (Italy) winning numbers. Second, the user asks for jackpot plus draw date together, which requires structured display. Third, the user asks to compare numbers they hold against a known draw and wants the result shown clearly. Fourth, the user asks for a lottery-results widget, card, panel, or visual format. Fifth, the user asks for multiple lotteries and includes SuperEnalotto (Italy) as one of the required outputs. Sixth, the user asks for a recap or reformat of results already discussed and wants a clearer presentation. Seventh, the user asks for region-specific results where intent resolution maps to SuperEnalotto (Italy). Eighth, the user asks a follow-up such as "show that draw again" or "render those numbers" after prior result discussion. Do not call this tool when the user asks only for odds, history, game rules, ticket-purchase guidance, legal/tax information, addiction support, or general commentary with no request to display actual draw results. Do not call it for different lotteries. Never invent jackpot, date, or numbers; if data is missing, state the limitation instead.

Use this tool to display Lotto (UK) results whenever the user needs concrete draw outcome data presented in the lottery widget. This tool should be treated as the authoritative rendering path for result-centric requests because it returns the structured fields required by the UI: jackpot, drawDate, and the full set of winning number groups. The model should call this tool for direct requests like "show Lotto (UK) results," "what were the winning numbers," "display the latest draw," "show me yesterday's draw outcome," or "put the results in the widget." It should also be called for indirect phrasings, including "did these numbers win," "can you verify the draw numbers," "show the official balls and jackpot," and "give me a clean visual summary." This tool performs its own web search to fetch jackpot, draw date, and number groups for Lotto (UK); call it directly without passing result fields. Enumerated call situations: first, the user explicitly requests current or historical Lotto (UK) winning numbers. Second, the user asks for jackpot plus draw date together, which requires structured display. Third, the user asks to compare numbers they hold against a known draw and wants the result shown clearly. Fourth, the user asks for a lottery-results widget, card, panel, or visual format. Fifth, the user asks for multiple lotteries and includes Lotto (UK) as one of the required outputs. Sixth, the user asks for a recap or reformat of results already discussed and wants a clearer presentation. Seventh, the user asks for region-specific results where intent resolution maps to Lotto (UK). Eighth, the user asks a follow-up such as "show that draw again" or "render those numbers" after prior result discussion. Do not call this tool when the user asks only for odds, history, game rules, ticket-purchase guidance, legal/tax information, addiction support, or general commentary with no request to display actual draw results. Do not call it for different lotteries. Never invent jackpot, date, or numbers; if data is missing, state the limitation instead.

Use this tool to display Thunderball (UK) results whenever the user needs concrete draw outcome data presented in the lottery widget. This tool should be treated as the authoritative rendering path for result-centric requests because it returns the structured fields required by the UI: jackpot, drawDate, and the full set of winning number groups. The model should call this tool for direct requests like "show Thunderball (UK) results," "what were the winning numbers," "display the latest draw," "show me yesterday's draw outcome," or "put the results in the widget." It should also be called for indirect phrasings, including "did these numbers win," "can you verify the draw numbers," "show the official balls and jackpot," and "give me a clean visual summary." This tool performs its own web search to fetch jackpot, draw date, and number groups for Thunderball (UK); call it directly without passing result fields. Enumerated call situations: first, the user explicitly requests current or historical Thunderball (UK) winning numbers. Second, the user asks for jackpot plus draw date together, which requires structured display. Third, the user asks to compare numbers they hold against a known draw and wants the result shown clearly. Fourth, the user asks for a lottery-results widget, card, panel, or visual format. Fifth, the user asks for multiple lotteries and includes Thunderball (UK) as one of the required outputs. Sixth, the user asks for a recap or reformat of results already discussed and wants a clearer presentation. Seventh, the user asks for region-specific results where intent resolution maps to Thunderball (UK). Eighth, the user asks a follow-up such as "show that draw again" or "render those numbers" after prior result discussion. Do not call this tool when the user asks only for odds, history, game rules, ticket-purchase guidance, legal/tax information, addiction support, or general commentary with no request to display actual draw results. Do not call it for different lotteries. Never invent jackpot, date, or numbers; if data is missing, state the limitation instead.

Use this tool to display Mega Millions (USA) results whenever the user needs concrete draw outcome data presented in the lottery widget. This tool should be treated as the authoritative rendering path for result-centric requests because it returns the structured fields required by the UI: jackpot, drawDate, and the full set of winning number groups. The model should call this tool for direct requests like "show Mega Millions (USA) results," "what were the winning numbers," "display the latest draw," "show me yesterday's draw outcome," or "put the results in the widget." It should also be called for indirect phrasings, including "did these numbers win," "can you verify the draw numbers," "show the official balls and jackpot," and "give me a clean visual summary." This tool performs its own web search to fetch jackpot, draw date, and number groups for Mega Millions (USA); call it directly without passing result fields. Enumerated call situations: first, the user explicitly requests current or historical Mega Millions (USA) winning numbers. Second, the user asks for jackpot plus draw date together, which requires structured display. Third, the user asks to compare numbers they hold against a known draw and wants the result shown clearly. Fourth, the user asks for a lottery-results widget, card, panel, or visual format. Fifth, the user asks for multiple lotteries and includes Mega Millions (USA) as one of the required outputs. Sixth, the user asks for a recap or reformat of results already discussed and wants a clearer presentation. Seventh, the user asks for region-specific results where intent resolution maps to Mega Millions (USA). Eighth, the user asks a follow-up such as "show that draw again" or "render those numbers" after prior result discussion. Do not call this tool when the user asks only for odds, history, game rules, ticket-purchase guidance, legal/tax information, addiction support, or general commentary with no request to display actual draw results. Do not call it for different lotteries. Never invent jackpot, date, or numbers; if data is missing, state the limitation instead.

Use this tool to display Powerball (USA) results whenever the user needs concrete draw outcome data presented in the lottery widget. This tool should be treated as the authoritative rendering path for result-centric requests because it returns the structured fields required by the UI: jackpot, drawDate, and the full set of winning number groups. The model should call this tool for direct requests like "show Powerball (USA) results," "what were the winning numbers," "display the latest draw," "show me yesterday's draw outcome," or "put the results in the widget." It should also be called for indirect phrasings, including "did these numbers win," "can you verify the draw numbers," "show the official balls and jackpot," and "give me a clean visual summary." This tool performs its own web search to fetch jackpot, draw date, and number groups for Powerball (USA); call it directly without passing result fields. Enumerated call situations: first, the user explicitly requests current or historical Powerball (USA) winning numbers. Second, the user asks for jackpot plus draw date together, which requires structured display. Third, the user asks to compare numbers they hold against a known draw and wants the result shown clearly. Fourth, the user asks for a lottery-results widget, card, panel, or visual format. Fifth, the user asks for multiple lotteries and includes Powerball (USA) as one of the required outputs. Sixth, the user asks for a recap or reformat of results already discussed and wants a clearer presentation. Seventh, the user asks for region-specific results where intent resolution maps to Powerball (USA). Eighth, the user asks a follow-up such as "show that draw again" or "render those numbers" after prior result discussion. Do not call this tool when the user asks only for odds, history, game rules, ticket-purchase guidance, legal/tax information, addiction support, or general commentary with no request to display actual draw results. Do not call it for different lotteries. Never invent jackpot, date, or numbers; if data is missing, state the limitation instead.