Skip to main content
Glama

Hourly forecast

get_hourly_forecast
Read-onlyIdempotent

Answers: what will the wind, gusts, temperature, rain, cloud and other conditions be at a place and time, including wind and gusts at chosen heights above ground, and what were they in past hours the plan includes. Returns hourly values in the user's units, each with its status against the user's thresholds. "Good" means within the user's own UAV Forecast limits, not safe; airspace, permissions, aircraft limits and battery are not included. Current factor keys: wind_at_altitude, max_altitude, temp_or_wind_chill, humidity, delta_t, precip_prob, precip_intensity, thunder_prob, cloud_cover, cloud_base, icing, visibility, sun_elevation, gps, kp, gps_kp, gust_at_altitude; unknown keys may appear. Anything the plan, region or data sources don't include is listed under "unavailable" with a reason (plan, region, source, setting).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "place": "<place>"
    },
    "name": "get_hourly_forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
hoursNoHow many hours from start.
placeYesA favorite location's name, a place name, "lat, lon" coordinates, or "here".
startNoLocal date or date-time; may be in the past within your plan's historical window.
localeNoBCP 47 language tag for labels.
factorsNoThe factors to read; without it, those with an enabled threshold plus wind and gust.
profileNoA saved settings profile's name, to answer with that profile's settings instead of the current ones.
altitudesNoHeights above ground (AGL) in altitude_units; without altitude_units, the user's altitude units (see get_my_settings). Each must be above 0: the lowest forecast wind is the surface wind at 10 m (33 ft), so ask for that for wind at ground level.
altitude_unitsNom or ft; set it whenever the user names a unit.

Output Schema

NameRequiredDescriptionDefault
daysNo
linkNo
noteNo
hoursNo
placeNo
rangeNo
unitsNo
sourceNoSource: UAV Forecast
statusYesok or subscription_required; others may appear.
messageNo
timezoneNo
now_localNo
historicalNo
unavailableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this a read-only, idempotent, non-destructive and non-open-world call, so the bar is lower, and the description still adds real context: values come back hourly in the user's units, each carries a status measured against the user's own thresholds, missing data is surfaced under "unavailable" with a plan/region/source/setting reason, and unknown factor keys may appear. The one gap is that it gives no sense of volume or cost for a 24-hour, 12-factor, 5-altitude request.

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

Conciseness4/5

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

The answer is front-loaded with the core question it resolves before moving into caveats and key enumeration, so an agent can stop reading early. The long inline list of factor keys mostly duplicates the schema enum and could have been compressed, but the trailing note that unknown keys may appear justifies keeping it.

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?

With an output schema present and full parameter documentation, the description only needs to explain semantics rather than shapes, and it does: threshold-status meaning, the significance of "Good", the "unavailable" mechanism and its reason codes, and the historical-window constraint. Nothing an agent needs in order to call this correctly is missing.

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

Parameters3/5

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

Schema coverage is 100%, so the schema already carries the per-parameter meaning, including the place formats, altitude units and the factors default rule. The description contributes little beyond that, mainly restating that altitudes are heights above ground and that results are in the user's units; it does add the useful caveat that the factor key list is not exhaustive.

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 opening clause names a specific verb-and-resource pair: hourly wind, gust, temperature, rain and cloud conditions at a place and time, including winds at chosen heights and past hours within the plan window. It implicitly separates itself from check_good_to_fly by warning that "Good" only means within the user's UAV Forecast limits and is not a safety verdict, though it never names the sibling.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the tool answers "what will conditions be" as opposed to whether to fly, and the note that airspace, permissions, aircraft limits and battery are excluded steers the agent away from treating this as a go/no-go check. There is no explicit "use X instead when Y" routing to check_good_to_fly or get_space_weather.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources