check_trip_weather
ChatGPTUse this when the user already has a plan — a trip, tour or work schedule, typed or pasted, in one to three versions — and asks whether the weather works for it. Shows each version as a row of its stops by day, a day's stops side by side in time order, each stop graded over its time_of_day (else its whole day) by its rules into levels, or without them Dry, Chance, or Likely by peak 3-hour precipitation odds (under 20%, 20–59%, 60%+). Days already over read Past; days past the 14-day forecast, Too far out. From a pasted plan, pass only the outdoor or weather-sensitive stops with their dates and any times it gives, one rule per kind of activity. Supply lat/lon coordinates you resolve from the user's request (a named place, address, or landmark) — this tool never reads the browser's location. Not for choosing places or days (get_weather_planner), one activity at one time (get_activity_outlook), timing one drive (compare_route_timings), or one place (get_weather_summary).
compare_route_timings
ChatGPTUse this when the user is timing one trip by car, bike, or on foot: when to leave, or where and how long to break ("leave now or in an hour?"). Shows 2–4 strips of the same route colored Clear, Near Limit, or Over Limit over time by one weather limit, with arrivals. Give 2–10 route points in order (towns that pin the way, every break stop; the server drives it in traffic), one SI limit with near_margin, and each strip's own departure (any day, any time) and breaks (up to three). Each strip ≤24h with breaks; last arrival within 7 days. Supply lat/lon coordinates you resolve from the user's request (a named place, address, or landmark) — this tool never reads the browser's location. Not for different routes (get_route_comparison), one place against limits (find_weather_windows or get_activity_outlook), places or multi-day trips (get_weather_planner or get_weather_comparison), a plain forecast (get_weather_summary), one variable (get_variable_forecast), or a map (get_weather_map).
find_weather_windows
ChatGPTUse this when the user asks when an activity fits their weather limits. Shows one place as three-hour windows rated Clear, Near Limit, Over Limit, or unavailable, one day per page. day/days select the opening day and dates answered; arrows browse the forecast. Pass one to four named above, below, or between limits with SI thresholds and near_margin. Use one between limit for a band; duplicate variables are rejected. Missing criteria prevent Clear; a known breach remains Over Limit. 3h precipitation sums are not prorated. Supply lat/lon coordinates you resolve from the user's request (a named place, address, or landmark) — this tool never reads the browser's location. Not for a plain forecast (get_weather_summary), one variable in depth (get_variable_forecast), comparing places (get_weather_comparison), or a map (get_weather_map).
get_activity_outlook
ChatGPTUse this when the activity, place, and time are all fixed ("stargazing at Joshua Tree Sat 9pm"). Shows one gauge per limit: the forecast at that time (nearest 3-hour step; rain and snow as the 3-hour total through it), its p10–p90 range if available, and the limit as three bands. Choose 1–4 limits the activity hinges on, even unnamed (stargazing: cloud cover, wind, dew point spread), and label each with why it matters to the user ("Steady telescope"). zone_labels renames the bands (default Good/Marginal/Bad). hour is required; SI thresholds take near_margin. Supply lat/lon coordinates you resolve from the user's request (a named place, address, or landmark) — this tool never reads the browser's location. Not for a span or open timing (find_weather_windows), a forecast (get_weather_summary), one variable (get_variable_forecast), places (get_weather_comparison or get_weather_planner), a trip (compare_route_timings), or a map (get_weather_map).
get_forecast_stability
ChatGPTUse this when the user asks how settled a forecast is or how it has changed — "is the forecast flip-flopping", "has the front's timing shifted", "how sure is Saturday's high". Shows how the latest WindBorne model runs (one every 6 hours) forecast ONE variable at one location, one day per card: older runs fade and the newest is solid, so drift reads at a glance; the reader steps to any day the runs cover. Precipitation and snowfall amounts draw one tick per run per 3-hour block. runs picks how many runs (default 10); moments mark the user's times; highlights shade SI threshold regions and must name the plotted variable. Supply lat/lon coordinates you resolve from the user's request (a named place, address, or landmark) — this tool never reads the browser's location. Not for the forecast itself (use get_variable_forecast), not for the general "what's the weather" question (get_weather_summary).
get_route_comparison
ChatGPTUse this when the user is choosing between different routes for one trip by car, bike, or on foot, all leaving at the same time ("I-5 or the coast road?", "which way stays dry?"). Shows 1–4 routes on a map, each colored Clear, Near Limit, or Over Limit along the road by one weather limit, with travel times; tapping a route opens its journey strip. Give each route a label and 2–8 points in order (the towns that make it that route, every break stop; the server drives it in traffic) with up to three breaks, one shared departure (omit to leave now), and one SI limit with near_margin. Each route ≤24h with breaks; arrival within 7 days. Supply lat/lon coordinates you resolve from the user's request (a named place, address, or landmark) — this tool never reads the browser's location. Not for one route at different departures or break plans (compare_route_timings), one place against limits (find_weather_windows), or a weather map (get_weather_map).
get_typical_weather
ChatGPTUse this when the user wants what a place's weather is usually like, past what a forecast can see: a trip months away, when to go, what to pack for a season ("what's Tokyo like in October", "best time to visit Lisbon", "how rainy is Bali in January"). Shows a typical year from 2016–2025 climate normals, never a forecast: each month's average daily high and low as bars on one temperature scale, and its average precipitation total. The answer carries all twelve months. Supply lat/lon coordinates you resolve from the user's request (a named place, address, or landmark) — this tool never reads the browser's location. Not for weather in the next 14 days, which the forecast covers (get_weather_outlook).
get_variable_forecast
ChatGPTUse this when the user wants ONE weather variable in depth — a wind window, a pressure trend, cloud cover through the day, "how much snow is coming". Shows a single WindBorne forecast variable for one location, one day per card; the reader steps to any day the forecast covers, so day/days only pick the opening day and how many days the written summary spans. moments mark the user's times on the chart; highlights shade SI threshold regions and must name the plotted variable. Supply lat/lon coordinates you resolve from the user's request (a named place, address, or landmark) — this tool never reads the browser's location. Not for the general "what's the weather" question (use get_weather_summary), not for comparing places (get_weather_comparison), not for ranking time slots against several limits (find_weather_windows), not for a regional view (get_weather_map).
get_weather_comparison
ChatGPTUse this when the user wants to compare two to four places or pick between destinations — "is Lisbon or Porto nicer this weekend". Shows places side by side for a whole local day or one served hour. day defaults to today in the first place; hour uses that place's clock. The reader can page through the forecast. All requested vars appear in the answer; the widget shows at most five rows, or three with extra places. Peak precipitation odds describe one 3-hour block; sums are not prorated across midnight. Supply lat/lon coordinates you resolve from the user's request (a named place, address, or landmark) — this tool never reads the browser's location. Not for one place (get_weather_summary or get_variable_forecast), finding a time slot (find_weather_windows), or a map (get_weather_map).
get_weather_context
ChatGPTUse this when you need WindBorne forecast data to reason with and the reply should not be a weather card: a text answer, input for another tool, or a look before choosing a card. Shows nothing; returns JSON: hourly MetaMesh rows per place in SI units at the place's UTC offset (precipitation totals the 3 hours ending at its row, every third row), plus sections asked for — conditions, climate normals, station observations, forecast ranges. day/days pick local days at the first place; days states the size cap. Supply lat/lon coordinates you resolve from the user's request (a named place, address, or landmark) — this tool never reads the browser's location. Not for showing the user weather: a day's summary (get_weather_summary), one variable (get_variable_forecast), places side by side (get_weather_comparison or get_weather_planner), activity windows (find_weather_windows), one plan against limits (get_activity_outlook), a trip (compare_route_timings), or a map (get_weather_map).
get_weather_heatmap
ChatGPTUse this when the user wants to see how ONE weather variable shifts across several places over time: when the rain reaches each site, how gusts build along the coast, which evenings stay dry at every stop. Shows two to 5 places as rows of 3-hour blocks shaded by metric: a chance of precipitation over a threshold (0.25 mm, any rain, when omitted), a variable's value, or one variable against a limit's thresholds. day/days set the span on the first place's clock, at least 2 days (5 when the user names none); time_of_day keeps those hours of each day. Supply lat/lon coordinates you resolve from the user's request (a named place, address, or landmark) — this tool never reads the browser's location. Not for one place (get_variable_forecast, or find_weather_windows against limits) or which places or days work best (get_weather_planner).
get_weather_map
ChatGPTUse this when the user wants to SEE weather over a region — a storm, a front, a regional pattern, "is there a storm coming toward Florida", 500 hPa heights over an ocean. Shows an animated WindBorne weather map in a fixed Web Mercator rectangle around a focus: precipitation, pressure and wind by default, or a temperature, water-vapor or 500 hPa preset; day/hour pick the opening frame in the focus's local time, including supported historical dates. Supply lat/lon coordinates you resolve from the user's request (a named place, address, or landmark) — this tool never reads the browser's location. Omit offsets for a centered 10,000 × 5,000 km map, or give all four edge offsets in projected km (width 10,000–20,000, height 5,000–12,000; may cross the antimeridian). Not for a point forecast (use get_weather_summary), not for one variable at one place (get_variable_forecast), not for comparing places (get_weather_comparison), not for ranking activity time slots (find_weather_windows).
get_weather_outlook
ChatGPTUse this when the user wants the days ahead at a glance for one place ("10-day forecast", "what's the week looking like", "weather for my trip next week"). Shows one row per local day: the forecast's own icon for that day's sky (under a rain or snow icon, the day's peak 3-hour chance of precipitation), and its low-to-high temperature as a bar on one scale every row shares, so warmer and cooler days read against each other; today's bar marks the current temperature. day is the first row (omit for today); days is the row count, 3–14. Supply lat/lon coordinates you resolve from the user's request (a named place, address, or landmark) — this tool never reads the browser's location. Not for one day in depth (get_weather_summary), one variable over time (get_variable_forecast), comparing places (get_weather_comparison or get_weather_planner), timing an activity against limits (find_weather_windows or get_activity_outlook), a trip (compare_route_timings), or a map (get_weather_map).
get_weather_planner
ChatGPTUse this when the user asks which places or days work best across several places — a route day by day, job sites through the week, where it stays dry this weekend. Shows two to 5 places as rows of a table, each cell Dry, Chance, or Likely by peak 3-hour precipitation odds (under 20%, 20–59%, 60%+), or graded by rate. day/days set the span, resolution its cells, time_of_day its hours. rank_by names a clear best per column in the answer; sequence marks a suggested visit order. 3h precipitation sums are not prorated. Supply lat/lon coordinates you resolve from the user's request (a named place, address, or landmark) — this tool never reads the browser's location. Not for checking a plan the user already made (check_trip_weather), one place (get_weather_summary or get_variable_forecast), a side-by-side day (get_weather_comparison), activity limits (find_weather_windows or get_activity_outlook), timing one drive or ride (compare_route_timings), or a map (get_weather_map).
get_weather_summary
ChatGPTUse this when the user asks about overall weather or a general forecast for a place. Shows sky, temperature range, precipitation amount and chance for one location, one day per page. day/days select the opening day and dates answered; arrows browse the 14-day forecast. moments mark times on both charts; highlights shade SI thresholds for temperature_2m or total_precipitation_3h. Amounts sum 3h blocks without prorating across midnight; peak odds refer to one 3h block, not the whole day. Supply lat/lon coordinates you resolve from the user's request (a named place, address, or landmark) — this tool never reads the browser's location. Not for one variable in depth (get_variable_forecast), comparing places (get_weather_comparison), finding activity windows under user limits (find_weather_windows), or a regional view (get_weather_map).
