Skip to main content
Glama

LiveDataLink

by io.github.blackboxfoundry
OverviewDiscussionsAdmin

faa_public_aviation_search_airports

Read-onlyIdempotent

Search LiveDataLink's self-hosted official FAA 28-day NASR snapshot for U.S. airports and other landing facilities. Returns FAA/ICAO identifiers, location, facility type/use/status, coordinates, elevation, runway counts and dimensions, tower/FAR 139 signals, pagination, and cycle provenance. Use this for 'find airports near a city', 'public-use airports in Ohio with a 5,000-foot runway', or to resolve an identifier before a profile call. Reference data only; not live airport status or NOTAMs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum facilities. Default 20.
queryNoFAA/ICAO id, airport/facility name, or city.
stateNoTwo-letter U.S. state or territory code.
offsetNoFacilities to skip. Default 0.
statusNoFAA operational or closure status. Omit to include all statuses.
facility_useNoFAA public-use or private-use classification.
facility_typeNoAirport, heliport, seaplane base, balloonport, gliderport, or ultralight facility.
response_formatNoHuman-readable markdown or machine-readable JSON. Default markdown.
min_runway_length_ftNoRequire at least one runway of this published length.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • addedInput schema / properties / limit / maximum
      Added value: +100
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / min_runway_length_ft / maximum
      Added value: +20000
    • addedInput schema / properties / min_runway_length_ft / minimum
      Added value: +0
    • changedInput schema / properties / min_runway_length_ft / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / offset / maximum
      Added value: +10000
    • addedInput schema / properties / offset / minimum
      Added value: +0
    • changedInput schema / properties / offset / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / query / maxLength
      Added value: +120
    • addedInput schema / properties / query / minLength
      Added value: +1
    • addedInput schema / properties / state / pattern
      Added value: +"^[A-Za-z]{2}$"
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, open-world safety profile. The description adds genuinely useful context beyond them: the data is a self-hosted 28-day NASR snapshot, includes cycle provenance, and is reference-only rather than live status/NOTAMs. It stops short of describing pagination mechanics despite mentioning pagination.

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?

Three dense sentences, front-loaded with the data source and scope, then returns, then usage, then the freshness caveat. No filler sentences; each one carries distinct information.

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?

With no output schema, the description compensates by enumerating the returned fields and cycle provenance, and it discloses the data source and its non-live nature. Combined with 100% parameter coverage, an agent has everything needed to select and invoke it correctly.

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 all 9 parameters are already documented, establishing a baseline of 3. The description's example queries imply parameter combinations (state + facility_use + min_runway_length_ft, query for city/name/id), adding marginal value over the schema without explaining any single parameter further.

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 (Search) and resource (U.S. airports and other landing facilities), names the exact data source (official FAA 28-day NASR snapshot), and enumerates the returned fields. It is clearly distinguishable from the sibling profile, compare_airports, and search_runways tools.

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 concrete use cases ('find airports near a city', 'public-use airports in Ohio with a 5,000-foot runway') and explicitly routes to the profile sibling via 'resolve an identifier before a profile call'. It also states a when-not ('not live airport status or NOTAMs'), though it does not distinguish from compare_airports or search_runways.

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

All LiveDataLink toolsInspect
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.

Resources