Get Daily Airport Temperature Highs

Give your Agent the airport name, country and dates. After confirming the airport and its local time, it requests the highest temperature found in the returned observations for each day, with available information about when readings were taken and gaps in the records.

Your AI

Use with your AI

For tasks with several steps, continue in the AI you already use.

CodexClaude CodeCursorWindsurfCline

View instructions

Use Toolmu to get daily airport temperature highs with https://toolmu.com/tools/get-daily-maxima-weather-underground for [airport name] in [country], from [start date] to [end date]. Verify the exact airport and its local time from a reliable airport source before preparing the query. Do not infer the airport clock from an associated city. If the airport or local time is unclear, ask a simple airport/location question or request [airport weather page link]; pause if it still cannot be confirmed. Act within my existing authorization and budget. Show each available local day high calculated from returned observations in Celsius, with any reported time of the high, counts and gaps. Keep source warnings and explain how missing observations limit the conclusion; do not present these as official published daily highs.

Task:
Show daily highs calculated from airport observations for [airport name] in [country], from [start date] to [end date], using the airport local days. Include available times of the highs, counts and gaps, and explain missing coverage.

Paste into your connected AI's conversation.

Connection guide

Up to 0.012 credits / call

The final charge is based on confirmed usage. Unused reserved credits return to your available balance.

Weather Underground

Get Daily Airport Temperature Highs

You receive

Available daily summaries show the highest temperature calculated from returned observations in Celsius, together with the time of that reading. Observation counts, the longest gap and first and last reading times help you judge how much of each local day is represented. Use the high and coverage details together when comparing days.

Start with your task

Show daily highs calculated from airport observations for [airport name] in [country], from [start date] to [end date], using the airport local days. Include available times of the highs, counts and gaps, and explain missing coverage.

What to know

These are highs calculated from returned observations, not official published daily highs. Missing records can hide a higher temperature, so counts and gap details do not prove whole-day coverage. Keep source warnings with the summaries.

Inputs & outputs

Inspect the current inputs, availability, and maximum charge before starting.

Input schema

Input schema
Field / Path	Type	Requirement	Meaning
queryParams`queryParams`	`object`	Required	Required fields `end_date, start_date, station_id, timezone_name`
End date`queryParams.end_date`	`string`	Required	The end of the requested history period, written as YYYYMMDD. To request one date, use the same value as start_date.
Start date`queryParams.start_date`	`string`	Required	The beginning of the requested history period, written as YYYYMMDD; for example, 20260930 means September 30, 2026.
Airport ICAO station code`queryParams.station_id`	`string`	Required	The airport weather station's ICAO code, such as KJFK or EFHK. Use icaoCode from a station search result; this lookup does not use a personal weather station ID.
Station country code`queryParams.country_code`	`string`	Optional	An optional two-letter ISO country code for the airport station, such as US or FI.
Timezone for local dates`queryParams.timezone_name`	`string`	Required	An IANA timezone name, such as America/New_York or Europe/Helsinki. It determines the local calendar day used to group observations; daylight-saving transitions are handled automatically.

View raw JSON

{
  "type": "object",
  "required": [
    "queryParams"
  ],
  "properties": {
    "queryParams": {
      "type": "object",
      "required": [
        "end_date",
        "start_date",
        "station_id",
        "timezone_name"
      ],
      "properties": {
        "end_date": {
          "type": "string",
          "description": "End date in YYYYMMDD format."
        },
        "start_date": {
          "type": "string",
          "description": "Start date in YYYYMMDD format."
        },
        "station_id": {
          "type": "string",
          "description": "Airport station ICAO code (e.g. EFHK, KJFK). Obtain from search endpoint's icaoCode field."
        },
        "country_code": {
          "type": "string",
          "description": "Two-letter ISO country code for the station (e.g. FI, US)."
        },
        "timezone_name": {
          "type": "string",
          "description": "IANA timezone name for local date grouping (e.g. Europe/Helsinki, America/New_York). DST transitions are handled automatically."
        }
      },
      "additionalProperties": false
    }
  },
  "additionalProperties": false
}

Result schema

No fixed output contract is available. Field types reflect saved result evidence; individual responses can differ.

Result schema
Field / Path	Type	Meaning
Local summary date`result.data.daily_maxima[].date`	`string`	The local calendar date represented by this entry, grouped using the requested timezone.
Highest returned temperature in Celsius`result.data.daily_maxima[].max_temp_c`	`number`	The highest temperature calculated from the returned observations for this local date, in degrees Celsius. Missing observations can conceal a higher temperature.
Observation count`result.data.daily_maxima[].observation_count`	`number`	The number of observations reported for the date. A count alone does not show whether every part of the day is covered.
Reported duplicate count`result.data.daily_maxima[].duplicate_count`	`number`	The number of records reported as duplicates for this date. Zero duplicates does not mean there are no missing observations.
Longest observation gap in minutes`result.data.daily_maxima[].largest_gap_minutes`	`number`	The longest reported interval between available observations, in minutes. Read it alongside the first and last observation times; it does not establish full-day coverage.
First observation in local time`result.data.daily_maxima[].first_observed_at_local`	`string`	The first available observation timestamp for this date in the requested local timezone. It marks the start of the returned records, not necessarily the start of the whole day's coverage.
Last observation in local time`result.data.daily_maxima[].last_observed_at_local`	`string`	The last available observation timestamp for this date in the requested local timezone. It shows where the returned records end.
Maximum-temperature observation in local time`result.data.daily_maxima[].max_observed_at_local`	`string`	The local timestamp supplied for the observation associated with the calculated maximum. Read it with max_temp_c and the local summary date.
Maximum-temperature observation in UTC`result.data.daily_maxima[].max_observed_at_utc`	`string`	The UTC timestamp supplied for the maximum-temperature observation. It describes the observation time, not the time the report was retrieved.
Maximum-temperature calculation source`result.data.provenance`	`string`	DERIVED_FROM_ROWS means the maxima were calculated from returned observation records. It does not identify a source-published official daily-high series.
Data source note`result.data.data_source_note`	`string`	The response's source warning. UNVERIFIED_TWC_AIRPORT_HISTORY_PROXY identifies unverified TWC airport-history proxy data; retain this warning with the summary.
Timezone used by the summary`result.data.request_metadata.timezone_name`	`string`	The timezone recorded for the request. Use it when interpreting local dates and local observation times.
Data retrieval time`result.data.request_metadata.retrieved_at`	`string`	When the historical report was retrieved. This is separate from the dates and times of the weather observations.

Additional notes

Source context

Data is delivered through the Weather Underground connector. Weather Underground data background. Keep the result's source note when sharing a daily summary.

Questions about this tool.

Inputs, results and details to know before running it.

Get connected

The day follows the confirmed airport local time. The assistant checks an airport source rather than assuming the clock from an associated city. If needed, it asks you to clarify the airport or share [airport weather page link]. If the airport or its local time remains unconfirmed, the lookup pauses.

Get Daily Airport Temperature Highs

Get Daily Airport Temperature Highs

You receive

Start with your task

What to know

Inputs & outputs

Input schema

Result schema

Source context

Fill in the airport and dates

Send the task and confirm

Read highs with coverage

Questions about this tool.

You receive

Start with your task

What to know

Inputs & outputs

Input schema

Result schema

Source context

Fill in the airport and dates

Send the task and confirm

Read highs with coverage

Questions about this tool.

Which day does a high belong to?

Do many observations mean a complete day?