weather

Provides current weather conditions and forecasts using free services – no API keys needed.

Tools

| Tool | Purpose | |------|---------| | http | GET requests to wttr.in and Open-Meteo (no auth_provider needed) | | device | get_location → current GPS coordinates (latitude, longitude) |

Get current location

{
  "action": "get_location"
}

Returns GPS coordinates, e.g. GPS: 51.5074, -0.1278 (Accuracy: 12m). Use latitude/longitude directly with Open-Meteo, or as {LAT},{LON} with wttr.in.

---

Service 1: wttr.in (primary)

Lightweight, human-readable weather data via wttr.in.

Current weather – compact one-liner

{
  "method": "GET",
  "url": "https://wttr.in/{LOCATION}?format=%l:+%c+%t+%h+%w",
  "response_format": "text"
}

Returns e.g. London: ⛅️ +8°C 71% ↙5km/h

Format codes: %c condition · %t temperature · %h humidity · %w wind · %l location · %m moon phase

IMPORTANT: wttr.in is a weather service only. NEVER use wttr.in for reverse geocoding or location lookups. The %l format code only works with city names, not coordinates. To resolve coordinates to a city name, always use Nominatim (see below).

Current weather – short format

{
  "method": "GET",
  "url": "https://wttr.in/{LOCATION}?format=3",
  "response_format": "text"
}

Returns e.g. London: ⛅️ +8°C

Full text forecast (today + 2 days)

{
  "method": "GET",
  "url": "https://wttr.in/{LOCATION}?T",
  "response_format": "text"
}

Today only

{
  "method": "GET",
  "url": "https://wttr.in/{LOCATION}?1&T",
  "response_format": "text"
}

Current conditions only (no forecast)

{
  "method": "GET",
  "url": "https://wttr.in/{LOCATION}?0&T",
  "response_format": "text"
}

Location encoding rules

• Replace spaces with +: New+York, San+Francisco
• Airport codes work: JFK, CDG, LHR
• Units: append &m for metric (default) or &u for USCS/Fahrenheit
• Umlauts can be used directly: München, Zürich

---

Service 2: Open-Meteo (fallback, JSON)

Use when wttr.in is unavailable or when you need structured JSON data. Free, no API key. Docs: https://open-meteo.com/en/docs

Current weather by coordinates

{
  "method": "GET",
  "url": "https://api.open-meteo.com/v1/forecast?latitude={LAT}&longitude={LON}&current_weather=true"
}

Returns JSON with current_weather.temperature, current_weather.windspeed, current_weather.weathercode.

Find coordinates for a city

Use the Open-Meteo geocoding API first:

{
  "method": "GET",
  "url": "https://geocoding-api.open-meteo.com/v1/search?name={CITY}&count=1"
}

Returns results[0].latitude and results[0].longitude.

Find city name for coordinates (Reverse Geocoding)

If you only have coordinates (e.g. from GPS or Open-Meteo) and need the place name, use the Nominatim reverse geocoding API (free, no API key):

{
  "method": "GET",
  "url": "https://nominatim.openstreetmap.org/reverse?lat={LAT}&lon={LON}&format=json&accept-language=en",
  "headers": { "User-Agent": "SannaBot/1.0" }
}

Returns JSON with address.city (or address.town / address.village for smaller places) and display_name (full human-readable address).

Use this when:

• Open-Meteo returns only coordinates and you need to tell the user the location name
• device → get_location gives GPS coords and you want to greet with "The weather in {city}…"
• The user asks "where am I?" and you need to resolve GPS coordinates to a place name

Full workflow (Open-Meteo)

With city name:

1. Geocode the city name → get latitude and longitude
2. Query the forecast API with those coordinates
3. Interpret weathercode (0 = clear, 1–3 = cloudy, 45–48 = fog, 51–55 = drizzle, 61–65 = rain, 71–75 = snow, 95 = thunderstorm)

Without city name (current location):

1. device → get_location → get latitude and longitude directly
2. Query the forecast API with those coordinates (skip geocoding)
3. Optionally: reverse-geocode via Nominatim to get a city name for the response
4. Interpret weathercode

---

Workflows

"What's the weather?" (no location given)

1. device → get_location → returns e.g. 51.5074, -0.1278
2. Reverse-geocode via Nominatim to get the city name: GET https://nominatim.openstreetmap.org/reverse?lat=51.5074&lon=-0.1278&format=json&accept-language=en → use address.city for the response
3. http → GET https://wttr.in/51.5074,-0.1278?format=%c+%t+%h+%w with response_format: "text" (note: no %l – use the city name from Nominatim instead)
4. Summarise: "In London it's partly cloudy, 14 degrees, 65% humidity."

"What's the weather in London?"

1. http → GET https://wttr.in/London?format=%l:+%c+%t+%h+%w with response_format: "text"
2. Read the result and summarise: "In London it's partly cloudy, 8 degrees, 71% humidity, light wind from the south-west."

"Weather forecast for Paris"

1. http → GET https://wttr.in/Paris?T with response_format: "text"
2. Summarise the multi-day forecast for the user

"Will it rain tomorrow in London?"

1. http → GET https://wttr.in/London?1&T with response_format: "text"
2. Check the forecast for rain indicators
3. Answer: "Tomorrow in London light rain is expected in the afternoon, around 12 °C."

"What's the temperature in New York right now?"

1. http → GET https://wttr.in/New+York?format=%t with response_format: "text"
2. Answer: "It's currently +5 °C in New York."

---

Examples

• "What's the weather?" → device → get_location, then query wttr.in with coordinates
• "Weather in Tokyo" → wttr.in/Tokyo?format=%l:+%c+%t+%h+%w
• "Forecast for Paris" → wttr.in/Paris?T
• "Will it rain tomorrow?" → wttr.in/{LOCATION}?1&T, check for rain
• "Temperature in Sydney" → wttr.in/Sydney?format=%t
• "What's the moon phase?" → wttr.in/?format=%m

Notes

• wttr.in is the preferred source – fast, no keys, human-friendly output
• Use response_format: "text" for wttr.in (it returns plain text, not JSON)
• Fall back to Open-Meteo if wttr.in returns an error or times out
• Always summarise the result in natural language – do not just read raw output
• If the user does not specify a location, use device → get_location to get GPS coordinates and query with those