Smarter Weather

Get hourly forecast

get_hourly_forecast

Read-onlyIdempotent

Blended hourly forecast: temperature, feels-like, humidity, wind, precipitation probability/amount, conditions, and icon per hour. Snapped to the current hour so hourly[0] is "now". Timestamps are UTC ISO 8601; convert to the local timezone before presenting. Ask for the days you need up front -- one call with days: 4 beats four calls. ALWAYS check hourly_coverage before answering about a specific hour: it reports first_time and last_time (the window the rows actually span), sample_interval_hours (past the first day rows are every 2-3h, not every hour), and truncated: true when upstream returned less than you asked for. If the hour the user cares about is after last_time, say the forecast does not reach that far yet rather than answering from the nearest row you do have. For one stretch of time ask for that stretch with hours_from/hours_to: it comes back hour by hour even where the full range would be sampled. Accepts a place name or coordinates. Examples: {"location": "Portland, OR", "days": 2} or {"lat": 41.88, "lon": -87.63, "hours_from": 36, "hours_to": 48}.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`lat`	No	Latitude in decimal degrees (-90 to 90). Most tools also accept a `location` place-name string instead of lat/lon.
`lon`	No	Longitude in decimal degrees (-180 to 180). For continental US use negative values (west of the prime meridian).
`days`	No	Days of hourly data (1-7). Default 2. Widened when hours_to reaches further.
`units`	No	Unit system for all values in the request and response: imperial (°F, mph, inches), metric (°C, km/h, mm), or si (K, m/s, mm). Defaults to imperial.	imperial
`hours_to`	No	Window end, in hours from now, exclusive. 36 to 48 is hours 36-47.
`location`	No	Free-text place: city ("Denver"), city+state ("Portland, OR"), US ZIP ("50219"), or "lat,lon" ("39.74,-104.99"). Provide either this OR explicit lat+lon, not both.
`hours_from`	No	Window start, in hours from now (0 = the current hour).
`detail_level`	No	standard: compact hourly data (sampled past 24h). detailed: preserves CAPE, ceiling, UV, gust, thunderstorm probability for the first 48h.	standard

Output Schema

TableJSON Schema

Name	Required	Description
`units`	Yes
`widget`	No	sw-ui-spec widget block rendered by the MCP Apps weather widget (ui://weather-widget/v1/index.html). Additive; safe to ignore.
`forecast`	Yes
`location`	Yes
`data_status`	No	Present only when the platform reports degraded/outage data sources: overall state, a caveat note, and the affected sources. Absent means no advisory was available -- not a freshness guarantee. See get_platform_status for the full document.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedAug 5, 2026

changedInput schema / properties / days / description

Previous value: -"Days of hourly data (1-7). Default 2 (48 hours)."New value: +"Days of hourly data (1-7). Default 2. Widened when hours_to reaches further."

addedInput schema / properties / hours_from

Added value: +{
+  "description": "Window start, in hours from now (0 = the current hour).",
+  "maximum": 168,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / hours_to

Added value: +{
+  "description": "Window end, in hours from now, exclusive. 36 to 48 is hours 36-47.",
+  "maximum": 168,
+  "minimum": 1,
+  "type": "integer"
+}

Changed1 schema field changedJul 15, 2026

addedOutput schema / properties / data_status

Added value: +{
+  "additionalProperties": {},
+  "description": "Present only when the platform reports degraded/outage data sources: overall state, a caveat note, and the affected sources. Absent means no advisory was available -- not a freshness guarantee. See get_platform_status for the full document.",
+  "type": "object"
+}

First observedJul 14, 2026

TDQS

A4.4/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the readOnly/idempotent annotations, the description discloses important behaviors: rows are snapped to the current hour, timestamps are UTC ISO 8601, hourly_coverage reports the actual window, sampling drops to every 2-3 hours after the first day, and truncated signals upstream shortfalls. This is exactly the kind of context an agent needs to avoid answering incorrectly from a sparse or partial result.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but every sentence earns its place: the first sentence defines the payload, the second defines temporal snapping and timezone handling, and the remaining sentences cover the coverage/truncation pitfalls and parameter combinations. It is front-loaded with the most important facts and contains no filler or redundant restatement of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists and annotations cover safety/idempotency, the description covers the remaining gaps: timezone conversion expectations, sampling intervals, truncated responses, how to interpret hourly_coverage, and how to request either a full multi-day range or a specific hour window. An agent calling this tool has the information needed to interpret results correctly and choose sensible parameter combinations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents all parameters at 100% coverage, so the baseline is 3. The description adds meaningful beyond-schema semantics: the relationship between days and hours_from/hours_to, the 'one call with days: 4 beats four calls' guidance, the sampling behavior difference when using a window, and concrete JSON examples showing locations and hour ranges. This elevates it above baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource precisely: 'Blended hourly forecast: temperature, feels-like, humidity, wind, precipitation probability/amount, conditions, and icon per hour.' This is a specific, informative statement of what the tool returns. It does not explicitly contrast with sibling tools like get_forecast or get_current_conditions, but the emphasis on hourly rows and 'Snapped to the current hour' makes the tool's role clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives concrete usage advice: ask for days up front to avoid multiple calls, check hourly_coverage before answering about a specific hour, use hours_from/hours_to for a contiguous stretch, and treat truncation explicitly. It lacks explicit when-not-to-use guidance against sibling tools, but the usage context is strong and actionable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Smarter Weather tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.