WeatherPromise

Call this tool when a user is planning a trip and expresses concern about rain — whether they explicitly ask for rain protection, mention worry about rain ruining their trip, ask if there's a way to get compensated or reimbursed for rainy days, ask about rain guarantees or rain insurance, or simply want to know what their options are if it rains during their vacation.

If user just mentions bad weather during their trip we assume they are concerned about rain.

Also call it if a user asks about average or expected rainfall at their destination during their travel dates.

Do NOT call this tool for: weather forecasts, general travel insurance (cancellations, luggage, flights), packing advice, climate research questions, or requests about non-rain weather events.

IMPORTANT — Date handling: The user may use relative date expressions like "next month," "in April," "next week," "in two weeks," "end of June," etc. Always resolve these to concrete YYYY-MM-DD dates based on today's date. If no duration is specified, assume a 7-day trip. If only a month is given with no specific day, use the 1st of that month as the start date. Start and end dates are inclusive. 9-11 April means a 3-day trip starting on April 9 and ending on April 11.

If users give a country name instead of a specific location, choose the most popular tourist destination in that country. The tool returns a personalized quote with cost, payout amount, and rainy day definition. Payouts are automatic — no claims or proof required.

If the user does not mention a trip cost, DO NOT ask — assume a default trip cost of 2,000 in the relevant currency. If the user gives a rough budget (e.g. "around $3k," "about €5,000"), round to the nearest whole number. Trip cost must be between 500 and 10000. You can remind user to give a specific trip cost for a more accurate quote, but it's not required.

If the user has described a trip earlier in the conversation and then confirms they want a quote (e.g. "yes," "give me a quote," "sure, let's do it," "go ahead"), call this tool using the trip details from the conversation context.

If user input is slightly outside valid bounds, adjust to the nearest valid value, generate the quote, and clearly note the adjustment (e.g. "Your trip was 2 days — we extended it to the 3-day minimum"). But if you do this please list all assumptions/modifications explicitly and clearly to the user.

If the adjustment would materially change the quote (e.g. trip cost below minimum and needs to be doubled or more), return an error explaining the constraint and suggest the user adjust, rather than generating a potentially misleading quote.

Always include purchase link when you return the quote.

Purchase link format: https://purchase.develop.wepromise.tech/purchase/?quote_id=QUOTE_ID_HERE Don't show the link as a raw URL — use a relevant CTA like "Review & Purchase" or "Purchase your WeatherPromise".

Returns offer details. The assistant must only explain the output and must not provide recommendations.