faa-airmen-registry-mcp-server

Faa Airmen Verify Certificate

faa_airmen_verify_certificate

Read-onlyIdempotent

Find releasable FAA airman records by exact Unique ID or name and read their certificate records. Use name mode to discover IDs, then use an ID for ratings or informational medical fields. Certificate type, level, rating, and type-rating filters must all match one certificate, and each match still returns all its certificates. While the operator's personal-data redaction is on (the default), name mode needs lastName and firstName, nameMatch prefix and city or ZIP filters are rejected, and city and ZIP are withheld. A missing or matching record is not a current licensing or operating-privilege determination.

Input Schema

Name	Required	Description
`city`	No	Exact city, 1–60 visible characters; requires operator-enabled location access and is rejected while personal-data redaction is on. Blank means unset.
`mode`	Yes	id requires uniqueId and forbids nonblank name/location fields and explicit nameMatch; name requires lastName, plus firstName while personal-data redaction is on, and forbids nonblank uniqueId.
`limit`	No	Maximum complete people or reference entries per page; default 10, maximum 50. A larger limit returns at most 50, with a notice.
`state`	No	Two-letter state or territory; trimmed and uppercased. Blank means unset.
`offset`	No	Zero-based offset; default 0, maximum 10000. Follow nextOffset or narrow filters at the cap.
`zipCode`	No	Five-digit ZIP or ZIP+4, preserving leading zeros; requires operator-enabled location access and is rejected while personal-data redaction is on. Blank means unset.
`lastName`	No	LAST NAME, which may include a suffix; the default words match finds SMITH JR from SMITH. 1–60 visible characters after normalization. Blank means unset.
`uniqueId`	No	Opaque FAA Unique ID returned by faa_airmen_verify_certificate in name mode, A or C plus seven digits, for example A9999999; not a certificate number. Trimmed and uppercased.
`firstName`	No	FIRST NAME, which usually includes middle names; the default words match finds JOHN ROBERT from JOHN. 1–60 visible characters after normalization. Blank means unset.
`nameMatch`	No	How each supplied name field matches; default words for name searches. words: the field equals the term or continues with a space after it; only a space separates words, so a hyphenated or apostrophe name is one word. exact: the whole field. prefix: the field begins with the term, also mid-word; rejected while personal-data redaction is on.
`ratingCodes`	No	One to eleven rating codes, repeats collapsed; every code must occur on the same certificate as every other requested credential, never across certificates.
`typeRatings`	No	One to eleven type-rating designators, repeats collapsed; every designator must occur on the same certificate as every other requested credential.
`certificateType`	No	One FAA certificate type letter, its description from faa_airmen_list_reference topic certificate_types (case-insensitive; underscore or space, such as remote pilot or flight_instructor), or CFI; selects people while retaining all their certificates.
`certificateLevel`	No	One level letter listed for the certificateType in faa_airmen_list_reference topic certificate_levels, such as A (airline transport pilot) with certificateType P; requires certificateType and matches the certificate's own level. Trimmed and uppercased; blank means unset.

Output Schema

Name	Required	Description
`error`	No	Present when the call failed. Absent on success.
`notice`	No	Snapshot limitations, absence guidance, source-quality notices for the returned records, and operational notices; may be empty.
`hasMore`	No	Whether another page is reachable within the offset cap.
`matches`	No	Separate identity candidates; never infer a single person from multiple matches.
`nextOffset`	No	Next reachable offset, or null when no next page is available.
`provenance`	No	Snapshot provenance, or null for static reference topics.
`totalCount`	No	Total matches after filtering, before paging.
`atPagingCap`	No	Matches remain but the next offset exceeds 10000; narrow the filters.
`piiRedacted`	No	Operator personal-data redaction: true withholds city, ZIP, and medical fields and limits searches to a full name or Unique ID.
`returnedCount`	No	Complete people or reference entries returned on this page.
`appliedFilters`	No	Every effective normalized selector, filter, and paging value.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 25, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Annotations only cover read-only/idempotent/closed-world; the description adds substantive behavior beyond them: redaction is on by default, name mode then requires firstName and lastName, nameMatch prefix and city/ZIP are rejected, city and ZIP values are withheld, and a missing or matching record is not a licensing determination. Those are exactly the operational and interpretive caveats an agent needs before calling.

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?

Five sentences, front-loaded with purpose and mode workflow before the redaction constraints and the disclaimer. Dense but every clause carries operational content; only the trailing licensing disclaimer is borderline, and it earns its place as a usage caveat.

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?

Output schema exists and pagination/limits live in the schema, so the description needn't restate returns. It covers mode gating, redaction effects, filter conjunction semantics, and the non-determinative nature of results. What it lacks is explicit routing against the five sibling tools for ratings, medical, and remote-pilot records.

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 description coverage is 100%, so the baseline is 3; the description goes beyond it by explaining the conjunction rule (certificate type, level, rating, and type-rating filters must all match one certificate while every match still returns all certificates) and by framing mode selection as a workflow rather than a bare enum.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (find releasable FAA airman records and read certificate records) plus the two lookup keys (exact Unique ID or name). The write-up distinguishes the two modes' outputs (ID mode for ratings/medical fields) but never names the sibling tools that own those adjacent tasks, so differentiation is inferential rather than explicit.

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?

Gives an explicit two-step workflow: name mode to discover IDs, then ID mode for ratings or informational medical fields. It also states which filters are rejected under redaction. It stops short of saying when to prefer faa_airmen_get_type_ratings, faa_airmen_check_medical_status, or faa_airmen_verify_remote_pilot over this tool.

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

All faa-airmen-registry-mcp-server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.