Skip to main content
Glama
Pradumnasaraf

Aviationstack MCP Server

by Pradumnasaraf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_airports

Search and page through the airport catalog to retrieve airport names, IATA/ICAO codes, and timezone info, with optional search to resolve a name to its IATA code for flight tools.

Instructions

List airports from the reference catalog, one page at a time, with optional text search. Each record has airport name, IATA and ICAO codes, city IATA code, country name and ISO2, timezone and GMT offset, alongside a pagination block carrying limit, offset and total. Use search to resolve an airport name to the IATA code the flight tools expect.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of airports to return per page, from 1 to 100.
offsetNoZero-based offset for pagination. Combine with limit and the total in the response to page through results.
searchNoOptional text matched against airport name and codes. Autocomplete search requires the Basic plan or higher, as does this endpoint.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.8.1
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of airports to return."New value: +"Maximum number of airports to return per page, from 1 to 100."
    • changedInput schema / properties / offset / description
      Previous value: -"Offset for pagination."New value: +"Zero-based offset for pagination. Combine with limit and the total in the response to page through results."
    • changedInput schema / properties / search / description
      Previous value: -"Optional airport search text for autocomplete."New value: +"Optional text matched against airport name and codes. Autocomplete search requires the Basic plan or higher, as does this endpoint."
  2. Changed1 schema field changedv1.7.0
    • addedInput schema / properties / limit / maximum
      Added value: +100
  3. Addedv1.6.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It transparently explains pagination behavior, optional search, and the shape of each record including the pagination block. It does not mention auth or rate limits, but for a read-only catalog listing the disclosed behavior is thorough and accurate.

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 tightly written in three sentences: a clear action statement, a record contents overview, and a practical use-case note. Every sentence contributes meaningful information, and the most important purpose is front-loaded.

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?

For a simple, all-optional-parameter list tool with an output schema present, the description covers everything an agent needs: operation, pagination semantics, record fields, search behavior, and the intended downstream use. No critical information appears missing.

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 coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by explaining how pagination works ('one page at a time', 'pagination block carrying limit, offset and total') and framing 'search' as the mechanism to resolve names to IATA codes for flight tools. This is useful contextual value that the parameter descriptions alone do not fully convey.

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 identifies the operation ('List'), the resource ('airports from the reference catalog'), and key distinguishing features like pagination and optional text search. It also explains each record's contents and the intended use case for resolving airport names to IATA codes, making it easy to differentiate from sibling list 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?

The description gives clear context for when to use this tool: when you need airport reference data or need to resolve an airport name to the IATA code expected by flight tools. It does not name alternatives or state explicit exclusions, but the resource focus and sibling names are sufficiently distinct that no confusion is likely.

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

Deploy Server

Other Tools