Skip to main content
Glama
Pradumnasaraf

Aviationstack MCP Server

by Pradumnasaraf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

flights_with_airline

Get live flights for a specific airline, optionally filtered by flight status, and view flight number, airports, departure times, status, delay, terminal, and gate to survey its current operations.

Instructions

Return live flights for one airline, optionally narrowed to a single flight status. Returns flight number, airline, departure and arrival airports with timezones, scheduled departure time, status, delay, terminal and gate. Use this to survey an airline's current activity; use get_flight_status when you already know the flight number.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
airline_nameYesAirline name to filter flights (for example: Delta Air Lines).
flight_statusNoOptional flight status filter. One of: scheduled, active, landed, cancelled, incident, diverted.
number_of_flightsYesMaximum number of flights to return, from 1 to 100.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.8.1
    • changedInput schema / properties / number_of_flights / description
      Previous value: -"Number of flights to return."New value: +"Maximum number of flights to return, from 1 to 100."
  2. Changed3 schema fields changedv1.7.0
    • addedInput schema / properties / flight_status
      Added value: +{
+  "default": "",
+  "description": "Optional flight status filter. One of: scheduled, active, landed, cancelled, incident, diverted.",
+  "title": "Flight Status",
+  "type": "string"
+}
    • changedInput schema / properties / number_of_flights / description
      Previous value: -"Number of random flights to return."New value: +"Number of flights to return."
    • addedInput schema / properties / number_of_flights / maximum
      Added value: +100
  3. Changed5 schema fields changedv1.6.0
    • addedInput schema / properties / airline_name / description
      Added value: +"Airline name to filter flights (for example: Delta Air Lines)."
    • addedInput schema / properties / number_of_flights / description
      Added value: +"Number of random flights to return."
    • addedInput schema / properties / number_of_flights / exclusiveMinimum
      Added value: +0
    • changedInput schema / title
      Previous value: -"flights_with_airlineArguments"New value: +"flights_with_airline_toolArguments"
    • changedOutput schema / title
      Previous value: -"flights_with_airlineOutput"New value: +"flights_with_airline_toolOutput"
  4. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral disclosure itself. It communicates the live nature of the data, the optional status narrowing, and exactly which fields will be returned. It does not discuss auth, rate limits, or empty-result behavior, but these are not critical for a read-only lookup.

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 sentences with no wasted words: purpose first, return fields second, routing to the sibling third. Every sentence contributes distinct value.

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?

The description, full parameter docs, and existing output schema together cover the main contract. Minor gaps remain around API limitations (rate limits, live-data freshness guarantees), but an agent knows what to call, with what inputs, and what kind of output to expect.

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 documents airline_name, flight_status, and number_of_flights. The description only restates the optional status narrowing and adds no new parameter-level meaning, matching the baseline for high schema coverage.

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 opens with a specific verb-resource pair ('Return live flights for one airline') and an optional filter, and then explicitly contrasts it with get_flight_status. An agent can tell exactly what this tool does and how it differs from its nearest sibling.

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 gives an explicit when-to-use cue ('survey an airline's current activity') and points to get_flight_status for the known-flight-number case, but it does not mention exclusions for historical or schedule-based siblings such as historical_flights_by_date. Context is clear, but exclusions are partial.

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