Skip to main content
Glama

Search the aircraft registry

search_aircraft
Read-only

Registry-wide aircraft search — the fleet / market-research search surface. Returns individual registered tails matching an AND-combined filter set (make/model, US state, city, year, tail number, current registrant name, on-market status, or geographic radius), with pagination and sorting. Resolve each model name to a make_model_id with search_make_models first; to cover several models in one search pass them as a list with condition "in". For population totals (e.g. "how many R182s in Oregon") prefer count_aircraft, which avoids paging. Each filter is {field_name, condition, value}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoRows per page, 1–200 (default 25).
offsetNoPagination offset (default 0).
filtersNoAND-combined filters; each is {field_name, condition, value}. Fields: make_model_id (numeric id), state (2-letter US code), city, year, tail_number, registrant_name (current FAA registrant / registered owner; substring via contains), seen_on_market ("true"/"false"), latest_list_date, location_point, registration_authority, registration_country, airworthiness_class. Conditions: is, is_not, contains, does_not_contain, in, not_in, lt, lte, gt, gte. For location_point use condition "within_<miles>" (e.g. "within_50") with value "lat,lon" (e.g. "45.52,-122.68"). To search SEVERAL make/models at once, use one clause with condition "in" and an array of ids (e.g. {field_name: "make_model_id", condition: "in", value: [1699, 1704]}) — that is a union. Do NOT repeat make_model_id in separate clauses: filters are AND-combined, so two of them match nothing. Spec filters (gt/gte/lt/lte only): engine_power_hp, useful_load_lbs (pounds), smoh_hours (engine hours since major overhaul); engine_make is text (is/contains, e.g. "LYCOMING"). ⚠️ These come from per-model performance specs and listing data and are NOT populated for every aircraft: engine power 75% of the fleet, weights 76%, engine make 78%, smoh_hours only 12% (84% of aircraft that have ever been listed — pair it with seen_on_market). Filtering on one EXCLUDES every aircraft with no value, so tell the user that when you use them. airworthiness_class (is/is_not/in/not_in) is the FAA classification from the aircraft's LATEST registration — this is how you search for EXPERIMENTAL / amateur-built aircraft. Tokens: standard, limited, restricted, experimental, provisional, multiple, primary, special_flight_permit, light_sport. ⚠️ 36% of the fleet has no certification recorded, so filtering on it excludes all of those; say so when you use it. 🔴 STATE OF REGISTRY: this registry is NOT US-only. ~115k aircraft (21.6% of it) are on one of 17 international registers, and they are concentrated by model — 41% of the R44 fleet, 21% of C152s, 10% of SR22s. An unfiltered count is a WORLD count, not a US one. Use registration_authority with an authority code (FAA, TCCA, CASA, ANAC, DGAC, AESA, DGACL, ILT, ACG, IAA, CAANO, NSAT, CAAI, CAABG, CAALV, DAC, CAAS, ECAA) or the cohort tokens "domestic" / "international"; or registration_country with an ISO-2 code or country name ("CA", "Canada"). Say which fleet a number covers whenever you report one. ⚠️ There is NO `country` filter. The v3 validator rejects one (`country` is not a CAVN column), and the underlying value is the FAA registrant's mailing address, NULL for every international aircraft — so it could not select them even if it were accepted. Use registration_country. ⚠️ International aircraft have registry identity but no US market history, so they carry no predicted_price and cannot be valued by tail.
sort_fieldNoSort key (default last_airborne_at).
sort_directionNoDefault desc.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesMatching registered tails.
metaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations cover readOnly/openWorld/destructive, but the description adds rich context beyond them: data coverage warnings (engine power 75%, weights 76%, smoh 12%, certification 36% missing), and the crucial registry state warning that ~21.6% are international and unfiltered counts are global. This is essential behavioral disclosure.

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

Conciseness4/5

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

Front-loads purpose and then moves into exhaustive filter mechanics and warnings. Information density is high and each sentence adds value, but it runs long and some repetition (e.g. filter structure stated twice) slightly harms scanability.

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?

Given the tool's complexity (5 params, nested filter object, enum-heavy fields), the description is complete: it covers return semantics (individual registered tails, pagination/sorting), data caveats, international registry scope, and workarounds. Output schema exists but the description still provides necessary operational context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds substantial meaning: filter structure {field_name, condition, value}, AND combination semantics, the union trick with condition 'in', location_point syntax "lat,lon" with within_<miles>, the fact that using a filter EXCLUDES missing-value aircraft, and the absence of a country filter with the recommended workaround.

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?

States a specific verb and resource ('aircraft search'), names the scope ('registry-wide', 'fleet / market-research search surface'), and distinguishes itself from siblings by referring to search_make_models and count_aircraft. An agent can identify its purpose without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when/when-not guidance: resolve model names with search_make_models first, prefer count_aircraft for population totals, use condition 'in' for multiple models. Naming sibling tools and conditions makes routing unambiguous.

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.