ADSBiq MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ADSBIQ_API_KEY | No | Required for aircraft queries; not required for startup or tool discovery. |
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_aircraftA | Get current public state for one ICAO hex aircraft. |
| nearby_aircraftB | Get at most 50 aircraft within at most 250 nautical miles. |
| network_statsA | Get bounded aggregate ADSBiq network statistics. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a distinct purpose: retrieving a single aircraft, finding nearby aircraft within a radius, and getting network-level statistics. There is no overlap or ambiguity between them.
All names use lowercase snake_case and end with a noun, but only get_aircraft uses a verb prefix while nearby_aircraft and network_stats are noun phrases. The pattern is still predictable and intuitive.
Three tools is appropriate for a focused, read-only ADS-B data service. Each tool adds a distinct query capability without unnecessary bloat.
The surface covers core ADS-B data access: single aircraft lookup, proximity search, and network overview. Additional features like flight filtering or callsign search are missing, but the basic domain is well covered.