Skip to main content
Glama

faa-airmen-registry-mcp-server

Faa Airmen List Reference

faa_airmen_list_reference
Read-onlyIdempotent

Read FAA certificate and rating codes, observed aircraft type designators, identity guidance, medical guidance, or local mirror status. Use these references to construct lookup filters and interpret snapshot limits. Static topics work before mirror initialization.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "topic": "<topic>"
    },
    "name": "faa_airmen_list_reference"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum complete people or reference entries per page; default 10, maximum 50. A larger limit returns at most 50, with a notice.
topicYesOne FAA vocabulary, interpretation guide, or mirror diagnostic topic.
filterNoLiteral case-insensitive substring over code and description, 1–80 normalized characters; vocabulary topics only. Blank means unset.
offsetNoZero-based offset; default 0, maximum 10000. Follow nextOffset or narrow filters at the cap.

Output Schema

NameRequiredDescriptionDefault
errorNoPresent when the call failed. Absent on success.
topicNoOne FAA vocabulary, interpretation guide, or mirror diagnostic topic.
noticeNoSnapshot limitations, absence guidance, source-quality notices for the returned records, paging notices (a clamped limit, the offset cap, or a page the response size budget ended before limit), and operational notices; may be empty.
entriesNoComplete matching reference entries for this page.
hasMoreNoWhether another page is reachable within the offset cap.
nextOffsetNoNext reachable offset, or null when no next page is available.
provenanceNoSnapshot provenance, or null for static reference topics.
totalCountNoTotal matches after filtering, before paging.
atPagingCapNoMatches remain but the next offset exceeds 10000; narrow the filters.
piiRedactedNoOperator personal-data redaction: true withholds city, ZIP, and medical fields and limits searches to a full name or Unique ID.
mirrorStatusNoSafe diagnostic state present only for mirror_status.
returnedCountNoComplete people or reference entries returned on this page. Fewer than limit means the results ended or the response size budget ended the page; while hasMore is true, the notice names the offset to continue from.
appliedFiltersNoEvery effective normalized selector, filter, and paging value.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedOutput schema / properties / mirrorStatus / properties / refreshState / description
      Previous value: -"Most recent refresh lifecycle state: idle when none is recorded or the last one completed, running while one is in progress within its 40-minute deadline, failed when the last one did not complete (see lastRefreshFailure)."New value: +"Most recent refresh lifecycle state: idle when none is recorded or the last one completed, running while one is in progress within its 40-minute deadline, failed when the last one did not complete (see lastRefreshFailure), unreadable when its record cannot be read or is not a valid refresh record, which leaves state and lookups unaffected; the entry guidance names the repair."
    • changedOutput schema / properties / mirrorStatus / properties / refreshState / enum
      Previous value: -[
      -  "idle",
      -  "running",
      -  "failed"
      -]New value: +[
      +  "idle",
      +  "running",
      +  "failed",
      +  "unreadable"
      +]
    • changedOutput schema / properties / notice / description
      Previous value: -"Snapshot limitations, absence guidance, source-quality notices for the returned records, and operational notices; may be empty."New value: +"Snapshot limitations, absence guidance, source-quality notices for the returned records, paging notices (a clamped limit, the offset cap, or a page the response size budget ended before limit), and operational notices; may be empty."
    • changedOutput schema / properties / returnedCount / description
      Previous value: -"Complete people or reference entries returned on this page."New value: +"Complete people or reference entries returned on this page. Fewer than limit means the results ended or the response size budget ended the page; while hasMore is true, the notice names the offset to continue from."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, and closed-world behavior. The description adds useful operational context, especially that static topics work before mirror initialization and that local mirror status is available. It does not discuss authentication or rate limits, but those are not indicated by the annotations either.

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?

Two sentences, front-loaded with what the tool reads and followed by practical usage context. There is no filler or redundant restatement of the schema.

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?

For a four-parameter read-only reference tool with full schema coverage, annotations, and an output schema, the description covers the purpose and the key initialization caveat. Remaining details such as pagination behavior and per-topic filtering rules are appropriately delegated to structured fields.

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 description coverage is 100%, so the schema already fully documents the topic enum, filter, limit, and offset. The description only implies filter and limit usage through phrases like 'construct lookup filters' and 'interpret snapshot limits', adding little syntax or constraint detail beyond the schema.

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?

The description uses a specific verb, 'Read', and enumerates the reference resources: FAA certificate and rating codes, type designators, identity/medical guidance, and mirror status. It does not explicitly name sibling verification tools, so sibling differentiation is implicit 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?

It states that these references should be used to construct lookup filters and interpret snapshot limits, and notes that static topics work before mirror initialization. This gives clear usage context, but it does not explicitly name alternatives or state when not to use this tool.

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.