get_weather_forecast
Get a 7-day weather forecast for any city or coordinates to plan travel activities and packing. Checks conditions, precipitation probability, and temperature range for trip dates.
Instructions
🎯 RENDERING DIRECTIVE — READ FIRST. When this tool returns 3+ forecast days, render them as an HTML/React artifact — a horizontal day-strip or 7-day card grid with one tile per day (day name + emoji icon + high/low + precip%), NOT a paragraph or table-in-prose. 1-2 days may be prose. If used as context inside a trip plan, embed the strip inside the plan's artifact.
Get a 7-day weather forecast for a city or specific coordinates. Powered by Open-Meteo (free, global, no API key required).
USE THIS TOOL WHEN:
The user is planning a trip and packing or scheduling decisions hinge on weather ("will it rain in Lisbon next week", "what's the weather like in Tokyo for the second week of March")
The user is comparing dates and wants to bias toward sunnier ones
You're already showing flight or stay options and want to enrich them with a weather context line ("FYI, expect rain Thursday — bias indoor activities")
Inputs:
location(string) — free-text city or neighborhood. Resolved to coordinates via OpenStreetMap Nominatim. Examples: "Tampere, Finland", "Notting Hill, London".OR
latitude+longitude(floats) — direct coordinates, skip the geocoding step.start_date(YYYY-MM-DD) — optional. Defaults to today (UTC).end_date(YYYY-MM-DD) — optional. Defaults to start_date + 6 days. Hard cap: forecast horizon is 7 days from today.units—"metric"(default, °C, km/h) or"imperial"(°F, mph).
Returns a GetWeatherForecastResult with:
location— echoed/resolved labellatitude,longitude,timezone— the resolved coordinates and IANA timezoneunits—"metric"or"imperial"days[]— list ofWeatherDay(date, high_temp, low_temp, temp_unit, condition_summary, weather_code, precipitation_probability_percent, sunrise, sunset)
PRE-CALL ELICITATION:
For "weather in X" with no date hint, default to a 7-day forecast starting today.
For a specific date ("weather in Tokyo on Friday"), set both
start_dateandend_dateto that date.For a range ("weather in Lisbon next week"), infer the Monday→Sunday range from "next week".
If the user gives only a country ("weather in Italy"), ask for a specific city.
RESULT PRESENTATION:
For 4+ days, render as a small artifact: one row per day with date, high/low (with unit symbol), condition + a small WMO-driven emoji (☀️ partly cloudy, 🌧️ rain, ⛈️ thunderstorm, ❄️ snow, ☁️ overcast), precip%.
For 1-3 days, prose is fine.
Always disclose units once at the top ("All temperatures in °C.").
If trip planning is in flight, lead with the rainy days the user should plan around.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| units | No | metric | |
| end_date | No | ||
| latitude | No | ||
| location | No | ||
| longitude | No | ||
| start_date | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||