reloadium.com

getWeatherForecast

Get an hourly weather forecast from the free Open-Meteo API for a location. Provide EITHER {latitude, longitude} (e.g. from getUserLocation) OR {locationName} (e.g. 'Lisbon' or 'Paris, France') to geocode it automatically. Returns a compact CSV — one row per 3-hour step — containing only the fields you ask for, to keep the response small: pass 'fields' to pick exactly what's needed instead of the default set, and 'days' (1-7, default 2) to bound how far ahead to fetch. Prefer this over web search for weather questions — it's more precise and far cheaper on context. For activity/timing questions that hinge on cloud cover over several days (stargazing, photography, hiking windows, outdoor events), call this ALONGSIDE webSearch rather than instead of it: use this tool for the actual verified cloud/precip numbers per day, and web search for context this API can't provide (moon phase, celestial events, venue recommendations) — then reconcile the two rather than repeating an unverified weather claim from a search result. Units: temperature/apparentTemperature in °C, wind/windGusts in km/h, windDirection in degrees, precipitation is a % probability, precipitationAmount in mm, visibility in km, humidity/clouds in %, weatherCode is a WMO code (0 = clear sky, higher = increasingly cloudy/wet/severe). When the user would benefit from seeing a multi-day trend rather than reading the raw CSV (e.g. 'when's the driest afternoon this week'), follow up with showChart (type:'line', one series per field you're highlighting) instead of describing the numbers in prose — the CSV's 3-hour rows are already close to that chart's {label, value} shape.

Page: /

Input schema

{
  "type": "object",
  "properties": {
    "latitude": {
      "type": "number"
    },
    "longitude": {
      "type": "number"
    },
    "locationName": {
      "type": "string",
      "description": "City/place name to geocode, e.g. 'Lisbon' or 'Paris, France'. Ignored if latitude/longitude are given."
    },
    "days": {
      "type": "number",
      "description": "How many days ahead to fetch, 1-7. Default 2."
    },
    "fields": {
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "temperature",
          "apparentTemperature",
          "precipitation",
          "precipitationAmount",
          "wind",
          "windGusts",
          "windDirection",
          "clouds",
          "humidity",
          "weatherCode",
          "uvIndex",
          "visibility"
        ]
      },
      "description": "Which hourly fields to include. Default: temperature, precipitation, wind, clouds."
    }
  }
}