Aviationstack MCP Server

future_flights_arrival_departure_schedule

Retrieve scheduled arrival or departure boards for an airport on future dates, from tomorrow through 12 months ahead, including flight times, airline, terminal, gate, and aircraft model.

Instructions

Return the scheduled arrival or departure board for an airport on a specific future date. Covers any date from tomorrow through about 12 months ahead, including the next 7 days. Returns airline, flight number, scheduled times, arrival airport, terminal, gate and aircraft model. Use flight_arrival_departure_schedule for today's board instead.

Input Schema

TableJSON Schema

Name	Required	Description
`date`	No	Date to query, in YYYY-MM-DD format. Any date from tomorrow through about 12 months ahead, including the next 7 days.
`airline_iata`	No	Optional airline IATA code filter (for example: UA).
`schedule_type`	Yes	Whether to return the arrival board or the departure board. One of: arrival, departure.
`airport_iata_code`	Yes	Airport IATA code (for example: SFO).
`number_of_flights`	No	Maximum number of flights to return, from 1 to 100.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.8.1Sep 19, 2026

changedInput schema / properties / date / description

Previous value: -"Future date in YYYY-MM-DD format."New value: +"Date to query, in YYYY-MM-DD format. Any date from tomorrow through about 12 months ahead, including the next 7 days."

changedInput schema / properties / date / examples

Previous value: -[
-  "2026-03-01"
-]New value: +[
+  "2027-03-01"
+]

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."

changedInput schema / properties / schedule_type / description

Previous value: -"Schedule type: arrival or departure."New value: +"Whether to return the arrival board or the departure board. One of: arrival, departure."

Changed2 schema fields changedv1.7.0Sep 16, 2026
- 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
```

Changed14 schema fields changedv1.6.0May 4, 2026

addedInput schema / properties / airline_iata / default
```
Added value: +""
```

addedInput schema / properties / airline_iata / description

Added value: +"Optional airline IATA code filter (for example: UA)."

addedInput schema / properties / airport_iata_code / description
```
Added value: +"Airport IATA code (for example: SFO)."
```
addedInput schema / properties / airport_iata_code / minLength
```
Added value: +1
```
addedInput schema / properties / date / default
```
Added value: +""
```

addedInput schema / properties / date / description

Added value: +"Future date in YYYY-MM-DD format."

addedInput schema / properties / date / examples
```
Added value: +[
+  "2026-03-01"
+]
```
addedInput schema / properties / number_of_flights / default
```
Added value: +5
```
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
```
addedInput schema / properties / schedule_type / description
```
Added value: +"Schedule type: arrival or departure."
```

changedInput schema / required

Previous value: -[
-  "airport_iata_code",
-  "schedule_type",
-  "airline_iata",
-  "date",
-  "number_of_flights"
-]New value: +[
+  "airport_iata_code",
+  "schedule_type"
+]

changedInput schema / title

Previous value: -"future_flights_arrival_departure_scheduleArguments"New value: +"future_flights_arrival_departure_schedule_toolArguments"

changedOutput schema / title

Previous value: -"future_flights_arrival_departure_scheduleOutput"New value: +"future_flights_arrival_departure_schedule_toolOutput"

First observedAug 15, 2025

TDQS

A4.5/5.0

Behavior4/5

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

No annotations are provided, so the description carries the burden. It openly states the future-date limitation, the fact that the board is scheduled rather than live, and the outputs returned. It doesn't discuss error conditions or default behavior when date is omitted, but those are minor for a read-style query tool.

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 tight sentences: the main action, the applicable date window, the output fields, and the sibling alternative. Every sentence earns its place and no information is repeated except the deliberate emphasis of the next-7-days coverage.

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 moderately parameterized tool with a rich input schema and an output schema, the description covers purpose, temporal scope, return contents, and the key alternative. Nothing essential to selecting or invoking the tool correctly is missing.

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%, so the schema already documents date format, airport code, airline filter, schedule_type values, and number_of_flights. The description adds no parameter-level meaning beyond emphasizing the future-date window, so the baseline of 3 is appropriate.

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 action and resource: returns the scheduled arrival/departure board for an airport on a future date. It further defines the date window and explicitly routes today's board queries to flight_arrival_departure_schedule, so it is clearly distinguished from the sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says this tool covers tomorrow through about 12 months ahead and names flight_arrival_departure_schedule as the tool to use for today's board instead. This gives clear when-to-use and when-not-to-use guidance.

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

Deploy Server