Skip to main content
Glama
Pradumnasaraf

Aviationstack MCP Server

by Pradumnasaraf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_airlines

Retrieve paginated airline records with IATA/ICAO codes, callsign, and operational status. Use search to resolve airline names to IATA codes for flight queries.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of airlines 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 airline 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 airlines to return."New value: +"Maximum number of airlines 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 airline search text for autocomplete."New value: +"Optional text matched against airline 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.4/5.0
Behavior4/5

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

No annotations are provided, and the description carries the behavioral burden well: it discloses one-page-at-a-time pagination, the pagination block with limit/offset/total, and the presence of operational status. It does not explicitly address rate limits or plan requirements in the description, but the schema already carries the Basic plan note and the operation is inherently read-only.

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?

The description is front-loaded with the core purpose and is free of filler. The field-list sentence is useful but partly duplicates what the output schema already documents, keeping it just below a perfect 5.

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 read-only, paged catalog-listing tool with all parameters described in the schema and an output schema available, the description is sufficient. It covers the operation, the return shape, pagination, and the key integration use case for flight tools.

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 telling the agent that search is the mechanism to resolve a user-supplied airline name to the IATA code expected by flight tools. It also frames limit/offset in terms of the pagination block returned.

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 and resource: 'List airlines from the reference catalog,' with pagination and optional search. The 'airlines' scope distinguishes it from sibling catalog tools like list_airports and list_routes, and the record-field list makes the resource concrete.

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 provides a clear practical use: 'Use search to resolve an airline name to the IATA code the flight tools expect,' which positions the tool as the reference lookup for flight-related siblings. It does not explicitly name when-not-to-use alternatives, so it misses the top tier.

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