Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ADSB_URLNoYour feeder's live snapshot (readsb / tar1090 path).http://localhost:8080/data/aircraft.json
ADSB_SITE_LATNoReceiver latitude for nearest-first overhead distances. Home-location PII — from 1Password, never committed. Unset = overhead without distances.
ADSB_SITE_LONNoReceiver longitude for nearest-first overhead distances. Home-location PII — from 1Password, never committed. Unset = overhead without distances.
ADSB_MCP_TOKENNoBearer token required on streamable-http transport when set.
ADSB_HTTP_TIMEOUTNoHTTP timeout in seconds.10

Instructions

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

This server publishes no instructions, or was last inspected before Glama recorded them.

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
aircraft_overheadA

Aircraft currently in range of the receiver, nearest first. The "what's that plane overhead right now" query. With the receiver location configured, each result carries distance_km + bearing; without it, results are listed newest-position-first and distance is null (set ADSB_SITE_LAT/LON).

    Args:
        max_results: cap on aircraft returned (default 10).
        include_grounded: include aircraft on the ground (default False — only airborne).
    
aircraft_nearA

Aircraft currently within radius_km of a given point (lat/lon you supply — e.g. a city), nearest first. Unlike aircraft_overhead this needs no receiver location: distance is measured from the point you pass.

    Args:
        latitude/longitude: the centre point to search around.
        radius_km: search radius in kilometres (default 50).
        max_results: cap on aircraft returned (default 10).
        include_grounded: include aircraft on the ground (default False).
    
find_aircraftA

Find aircraft currently in range by a partial match on callsign, ICAO hex, or registration (case-insensitive). Returns matches even if they have no position yet.

    Args:
        query: text to match against callsign / hex / registration (e.g. "LAN", "e80", "CC-B").
        max_results: cap on matches returned (default 10).
    

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 3 tools

Disambiguation4/5

aircraft_overhead and aircraft_near are both 'aircraft in range, nearest first' spatial queries, but the descriptions clearly distinguish them (implicit receiver location vs. an explicit lat/lon you supply). find_aircraft is a clearly separate identifier-lookup path, so an agent can pick correctly.

Naming Consistency3/5

Two tools follow an aircraft_<modifier> pattern while the third is a verb_noun form (find_aircraft), and none use a consistent verb prefix. It is still readable and unprefixed-domain-consistent, but the convention is mixed.

Tool Count3/5

Three tools is on the thin side even for a narrow, read-only ADS-B query domain. It is defensible since each tool covers a distinct query mode, but the surface feels minimal.

Completeness3/5

Core live queries (overhead, radius, identifier lookup) are covered, but there is no tool for detailed single-aircraft data, historical/track positions, or receiver/feeder status. Agents can work around these gaps but cannot fully answer common questions like a plane's route or recent track.

Maintenance

ActivityMaintained
ResponsivenessNo issues