Skip to main content
Glama

Check good to fly

check_good_to_fly
Read-onlyIdempotent

Answers: can I fly my drone now, when today or this week, where (compare up to 5 places), which day is best, and why not. Judges every hour against the user's own thresholds, flying hours and profile, and returns good windows, the runs of hours that fail and why, per-day summaries for longer ranges, and weather warnings in effect. "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. Current notice kinds: weather_alert; more kinds 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": {
      "places": "<places>"
    },
    "name": "check_good_to_fly"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoLocal date or date-time; exclusive for a date-time, inclusive for a date.
daysNoFrom now to local midnight after this many days (1 = the rest of today). Not with start/end or hours.
hoursNoFrom now for this many hours. Not with start/end or days.
startNoLocal date (YYYY-MM-DD) or date-time (YYYY-MM-DDTHH:MM) at the place.
localeNoBCP 47 language tag for labels.
placesYesFavorite location names, place names, coordinates, or "here".
profileNoA saved settings profile's name, to answer with that profile's settings instead of the current ones.

Output Schema

NameRequiredDescriptionDefault
linkNo
noteNo
unitsNo
placesNo
sourceNoSource: UAV Forecast
statusYesok or subscription_required; others may appear.
messageNo
coarsenedNo
unavailableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and non-open-world, so the safety profile is covered. The description goes well beyond that by explaining that every hour is judged against the user's thresholds, that failures are returned as runs with reasons, that longer ranges produce per-day summaries, and that anything unsupported appears under 'unavailable' with a plan/region/source/setting reason.

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

Conciseness3/5

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

The lead sentence is excellent and front-loaded, but the trailing enumeration of factor keys and notice kinds is long and partly duplicates what the existing output schema already carries. The caveat sentences are dense but each conveys a real constraint, so the bulk is not wasted, only over-detailed.

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?

For a 7-parameter tool with a full output schema, the description covers everything an agent needs: what decision it answers, what 'good' means, what is out of scope, how unsupported data is surfaced, and how to interpret failure runs and per-day summaries. Nothing material is missing.

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?

Schema description coverage is 100%, so the baseline is 3. The description still adds meaning beyond the schema by emphasizing the up-to-5-place comparison mode and that profile selection substitutes a saved settings profile for the current one, which clarifies intent rather than repeating field text.

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

Purpose5/5

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

The opening sentence states a specific decision verb and resource: answers whether the user can fly a drone now, today, this week, across up to 5 places, and which day is best. It also implicitly separates itself from the sibling get_hourly_forecast by framing the output as a threshold-judged verdict rather than raw forecast data.

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?

It clearly bounds when the answer is applicable by defining 'good' as within the user's own UAV Forecast limits and explicitly excluding airspace, permissions, aircraft limits and battery. That is strong when-not-to-rely guidance, but it never names a sibling tool to use for those excluded concerns or for raw hourly data.

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