WeatherPromise

Tools (1)

Extracted live via the executor SDK.

• generate_quote

  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 the user mentions bad weather during their trip, assume they are concerned about rain and call this tool.

  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.

  Examples of date parsing:

  • "April 9-11" → start: April 9, end: April 11 (3-day trip)
  • "9 to 11 April" → start: April 9, end: April 11 (3-day trip)
  • "from the 9th to the 11th of April" → start: April 9, end: April 11 (3-day trip)
  • "next week" → 7-day trip starting next Monday
  • "end of June" → 7-day trip starting June 25

  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 may remind the user that a specific trip cost yields a more accurate quote, but it is 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"). List all assumptions and modifications explicitly and clearly.

  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 ask the user to adjust, rather than generating a potentially misleading quote.

  IMPORTANT: Always include the purchase link when returning the quote.

  Purchase link format: https://purchase.weatherpromise.com/purchase/?quote_id=QUOTE_ID_HERE Do not show the link as a raw URL — use a relevant CTA like "Review & Purchase" or "Purchase your WeatherPromise".

  Return the offer details only. Do not make recommendations.