Skip to main content
Glama
lichen911

Aviation MCP Server

by lichen911

query_aircraft

Search real-time global aircraft data by callsign, registration, type, location, squawk code, or ICAO hex. Access military or privacy addresses.

Instructions

Query real-time aircraft data from ADS-B Exchange.

You can search for aircraft by various criteria including callsign, registration, aircraft type, location, squawk code, ICAO hex, or get special categories like military aircraft or aircraft with privacy addresses.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueNoThe search value (callsign, registration, type code, etc.). Not required for 'military' or 'privacy' queries.
radiusNoSearch radius in nautical miles for location queries
latitudeNoLatitude for location-based queries (-90 to 90)
longitudeNoLongitude for location-based queries (-180 to 180)
query_typeYesType of query to perform. Options: - "callsign": Search by flight callsign (e.g., 'UAL123') - "registration": Search by aircraft registration (e.g., 'N12345') - "aircraft_type": Search by aircraft type (e.g., 'B738', 'A320') - "icao_hex": Search by ICAO hex code (e.g., 'A12B34') - "squawk": Search by transponder squawk code (e.g., '7700') - "location": Search within radius of coordinates - "military": Get all military aircraft - "privacy": Get all aircraft with privacy ICAO addresses

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions 'real-time' data, implying a read operation, but does not disclose rate limits, data freshness, authentication needs, or any limitations. Minimal behavioral transparency.

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

Conciseness5/5

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

The description is two sentences long. The first sentence states the core purpose, and the second lists search criteria. Every sentence earns its place without redundancy. Front-loaded and efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 5 parameters and an output schema exists, the description covers the query types and parameter usage well. It lacks usage caveats (e.g., rate limits, error handling) but output schema likely documents return structure. Overall complete for typical use.

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 coverage is 100%, baseline 3. The description adds significant value by explaining the meaning of each query_type and the conditions for 'value', 'radius', 'latitude', and 'longitude' parameters. It clarifies which parameters are needed for different query types, exceeding the schema's descriptions.

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 description clearly states the tool's purpose: 'Query real-time aircraft data from ADS-B Exchange.' It lists specific search criteria, distinguishing it from the sibling 'query_registration' which likely focuses on registration lookups. The verb 'Query' and resource 'aircraft data' are specific.

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?

The description explains when to use each query_type (e.g., 'callsign', 'military'), providing explicit context. However, it does not include when-not-to-use or compare directly with the sibling tool 'query_registration', which would improve guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lichen911/aviation-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server