Skip to main content
Glama

faa-aircraft-registry-mcp-server

by io.github.cyanheads

faa-aircraft-registry-mcp-server: get registration status

faa_get_registration_status
Read-onlyIdempotent

Resolve whether a US civil aircraft N-number is active, deregistered, reserved, or unknown, including the available registration and airworthiness status. Use this rather than faa_lookup_registration when a number may be inactive. A number that was never issued returns recordType "unknown" — a valid, informative answer, not an error. Accepts "N12345" or "12345".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nNumberYesUS registration N-number to resolve. Accepts "N12345" or "12345" (leading N optional). Shape: 1–5 characters — a leading digit 1–9, then digits, optionally ending in 1–2 letters (I and O are unused).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoPresent when the call failed. Absent on success.
statusNoRegistration/cancellation status as code + label (active and deregistered records).
nNumberNoNormalized N-number without the leading "N".
purgeDateNoScheduled purge date, YYYY-MM-DD (reserved records).
cancelDateNoCancellation date, YYYY-MM-DD (deregistered records).
recordTypeNoResolved registration state: active, deregistered, reserved, or unknown.
reserveDateNoDate the number was reserved, YYYY-MM-DD (reserved records).
modeSCodeHexNoMode S code in hex / ICAO 24-bit address (deregistered records).
serialNumberNoManufacturer serial number (deregistered records).
certIssueDateNoCertificate issue date, YYYY-MM-DD (active records).
expirationDateNoRegistration expiration date, YYYY-MM-DD (active records).
nNumberDisplayNoN-number with the leading "N" for display.
typeReservationNoType of reservation as code + label (reserved records).
nNumberForChangeNoThe N-number this reservation changes to/from (reserved records).
airworthinessDateNoAirworthiness certificate date, YYYY-MM-DD (active records).
airworthinessClassNoAirworthiness classification as code + label (active records).
expirationNoticeDateNoDate an expiration notice was sent, YYYY-MM-DD (reserved records).
manufacturerModelCodeNo7-char manufacturer/model/series code (deregistered records).

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, covering safety. The description adds the important behavioral clarification that an unissued number returns recordType 'unknown' as a valid answer, not an error, which goes beyond the structured annotations. This adds genuine context for interpreting responses.

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 three sentences with no redundant wording. It front-loads the core purpose, then provides usage guidance, and finally clarifies input format. Every sentence earns its place, making it extremely concise yet informative.

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?

The tool is a single-parameter resolver and the description covers the input format, the semantic output categories, the 'unknown' handling, and the distinction from its primary sibling. With an output schema present and annotations for idempotence, nothing an agent needs to correctly invoke and interpret this tool is missing.

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

Parameters3/5

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

Schema coverage is 100% for the single nNumber parameter, which already includes format details (leading N optional, character shape). The description reinforces this ('Accepts "N12345" or "12345"') but adds no new semantics beyond the schema's own description, so a baseline 3 is appropriate.

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 verb ('Resolve') and resource ('US civil aircraft N-number'), and specifies the possible outcomes: active, deregistered, reserved, or unknown. It also explicitly contrasts with the sibling tool 'faa_lookup_registration' when a number may be inactive, making differentiation unambiguous.

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?

The description provides explicit guidance: 'Use this rather than faa_lookup_registration when a number may be inactive.' This names the alternative and the exact condition for selection, leaving no ambiguity for the agent.

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

All faa-aircraft-registry-mcp-server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.7/5.0
Disambiguation5/5

Each tool has a clear and distinct purpose: faa_get_aircraft_type decodes a code to specs, faa_search_aircraft_types discovers codes by name; faa_lookup_registration gets full details for active N-numbers, faa_get_registration_status handles inactive or unreserved ones; faa_search_registrations searches by criteria. Descriptions explicitly clarify overlaps, so agents can reliably choose the right tool.

Naming Consistency5/5

All tools follow a uniform 'faa_verb_noun' pattern with consistent verb choices (get, lookup, search). The naming is predictable and makes the toolset easy to navigate.

Tool Count5/5

Five tools is ideal for a focused registry server. Each tool provides a necessary function (search, decode, status check, full lookup) without redundancy, covering the core workflow in a lean set.

Completeness5/5

The toolset covers all key operations for a read-only aircraft registry: searching registrations and aircraft types, looking up full records, and checking registration status across all files. There are no obvious gaps for the intended use case.

Resources