Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
FLIGHTOPS_OPENSKY_CLIENT_IDNoOpenSky API client ID (from Account → API Client at opensky-network.org). Required to unlock the traffic and movement tools.
FLIGHTOPS_OPENSKY_CLIENT_SECRETNoOpenSky API client secret, paired with FLIGHTOPS_OPENSKY_CLIENT_ID. Required to unlock the traffic and movement tools.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Use this server for questions about the operational state of an airport and the traffic around it.

Rules that the tools will enforce:

  1. Resolve identifiers first. resolve_airport is offline and free; it returns ICAO (ident), IATA, name and coordinates. Never guess a coordinate.

  2. airport_live_traffic, airport_movements and disruption_triage spend OpenSky API credits. Prefer one disruption_triage call over three separate ones.

  3. airport_weather needs no credentials and no credits.

  4. Absence of data is not evidence. Each payload lists unknowns; if it is non-empty, say so instead of concluding that operations are normal.

  5. This server is advisory. It reports observations and flags; it never authorises an operational decision.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
resolve_airportA

Resolve an airport from an ICAO/IATA code or a name fragment.

Offline and free: reads the bundled OurAirports reference database, so it
costs no API credits and works with no credentials configured.

Args:
    query: ICAO (ESGG), IATA (GOT), or part of an airport name.
    limit: Maximum matches to return (1-20).
airport_live_trafficA

Return aircraft currently within a radius of an airport.

Costs 1 OpenSky credit for a box up to 25 square degrees, up to 4 for a very
large radius. Aircraft are sorted by most recently heard.

Args:
    airport: ICAO code, e.g. ESGG.
    radius_nm: Search radius in nautical miles (5-200).
    max_aircraft: Cap on returned aircraft (1-200).
airport_movementsA

List estimated arrivals and/or departures for an airport.

Each direction costs 4 OpenSky credits for a live window of under 24 hours.
OpenSky derives these movements from ADS-B, so they are estimates: the
origin/destination fields are inferred from the first and last seen position.

Args:
    airport: ICAO code, e.g. ESGG.
    direction: "arrival", "departure", or "both".
    window_minutes: Look-back window in minutes (5-60; OpenSky serves at most
        one hour of history).
airport_weatherA

Return the latest METAR and TAF for an airport, plus impact flags.

Needs no credentials and spends no OpenSky credits.

Args:
    airport: ICAO code, e.g. ESGG.
disruption_triageA

Assess whether an airport is currently disrupted: weather, traffic, movements.

This is the composite tool an agent should reach for first. It makes one
weather call (free), one movements call per direction and one traffic call
(OpenSky credits), then reports severity together with its reasons and its
unknowns. Severity is advisory only.

Args:
    airport: ICAO code, e.g. ESGG.
    radius_nm: Traffic search radius in nautical miles (5-200).
upstream_statusA

Report upstream health, credit spend and credential state.

Use before blaming the data: it separates "no credentials", "rate limited"
and "quiet airspace".

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 6 tools

Disambiguation4/5

Each tool targets a fairly distinct concern (weather, live traffic, movements, health, airport lookup), and descriptions explicitly separate free vs credit-spending calls. The main overlap is disruption_triage, which internally duplicates weather/traffic/movements, so an agent must judge whether to call the composite or the primitives — the description guides this but does not eliminate the choice. airport_live_traffic vs airport_movements is also a subtle distinction (aircraft currently present vs inferred arrivals/departures) that takes careful reading.

Naming Consistency3/5

All names are snake_case and readable, but the pattern is mixed: three tools use an 'airport_' prefix while disruption_triage, upstream_status, and resolve_airport do not. Verb style is also inconsistent — resolve_airport is verb_noun while the rest are noun-first (noun_noun or adjective_noun), so there is no predictable verb_noun convention to rely on.

Tool Count5/5

Six tools is well within a tight, purposeful scope for an airport-centric flight ops server. Every tool has a clear job: reference lookup, weather, traffic, movements, composite triage, and diagnostics — no filler or near-duplicates that could be consolidated without losing function.

Completeness4/5

The read-only airport situational-awareness domain is well covered: weather, live traffic, movements, composite severity, identifier resolution, and upstream/credential diagnostics with an explicit escape hatch for failures. Minor gaps remain — no aircraft/callsign-level lookup, no historical or delay-statistics access beyond the one-hour movements window, and no way to pull deeper airport metadata from resolve_airport.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues