Skip to main content
Glama

Aviationstack Future Flights

aviationstack_future_flights
Read-onlyIdempotent

Scheduled future flights at one airport, from Aviationstack's /flightsFuture endpoint, what flies a route on a day next week. Requires an IATA airport code, a direction (departure or arrival), and a date; returns each flight's number, airline, aircraft model, and scheduled terminal/gate/time. Aviationstack's booking-view window for this endpoint currently covers only the next 7 days (apilayer notice, 2026-10-06): date must be between tomorrow and 7 days from today, a date outside that window is refused before the call is made, not after a wasted round trip.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "date": "2026-10-09",
      "type": "departure",
      "iataCode": "JFK"
    },
    "name": "aviationstack_future_flights"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesFuture date, format YYYY-MM-DD, must fall within tomorrow through 7 days from today (UTC), Aviationstack's current flightsFuture window.
typeYesWhether to return flights scheduled to depart or arrive at iataCode
limitNo1-100 (default 100)
offsetNo0-based offset
iataCodeYes3-letter IATA airport code whose schedule to look up (e.g. "JFK")
airline_iataNoFilter by airline IATA code
airline_icaoNoFilter by airline ICAO code
flight_numberNoFilter by flight number

Output Schema

NameRequiredDescriptionDefault
dataNo
data_as_ofNoISO timestamp when this response was fetched live from Aviationstack
paginationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Future date, format YYYY-MM-DD, must fall within tomorrow through 7 days from today (UTC) — Aviationstack's current flightsFuture window."New value: +"Future date, format YYYY-MM-DD, must fall within tomorrow through 7 days from today (UTC), Aviationstack's current flightsFuture window."
  2. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds real value by disclosing the endpoint's 7-day booking window and the pre-flight validation that rejects bad dates before a round trip, but it stops short of describing pagination behavior or result caps.

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?

Front-loads the core purpose, then the required inputs, then the return shape, then the window caveat in a logical order. The single sentence is long and carries a parenthetical citation that is slightly heavier than needed, but nothing is redundant.

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?

An output schema exists, so return values are already structured data; the description nonetheless previews the key fields. Required inputs, the temporal constraint, validation behavior, and the endpoint's provenance are all covered, leaving nothing an agent needs to call 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 coverage is 100% and every property already carries its own description, including the date window and the departure/arrival enum, so the description adds little beyond restating them. The optional filters (airline_iata, airline_icao, flight_number, limit, offset) are not mentioned in the description at all.

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 ("Scheduled future flights at one airport"), names the upstream endpoint (/flightsFuture), and narrows the scope to a single-airport, one-day schedule. An agent can immediately tell this apart from a general flights or archive tool.

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?

Explicitly states the required inputs (IATA code, direction, date) and the exact time window (tomorrow through 7 days out), including that out-of-window dates are refused before the call. It never names a sibling as the alternative for dates outside the window, which is the one remaining gap.

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.