Aviationstack MCP Server

flight_arrival_departure_schedule

Get today's airport arrival or departure board by IATA code, with optional airline filter. Shows flight times, terminals, gates, and delays.

Instructions

Return today's arrival or departure board for an airport, optionally filtered by airline name. Returns airline, flight number, scheduled, estimated and actual times, terminals, gates and departure delay per flight. Covers the current day only: for any later date use future_flights_arrival_departure_schedule instead.

Input Schema

TableJSON Schema

Name	Required	Description
`airline_name`	No	Optional airline name filter.
`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.

Changed2 schema fields changedv1.8.1Sep 19, 2026

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
```

Changed11 schema fields changedv1.6.0May 4, 2026

addedInput schema / properties / airline_name / default
```
Added value: +""
```
addedInput schema / properties / airline_name / description
```
Added value: +"Optional airline name filter."
```
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 / 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_name",
-  "number_of_flights"
-]New value: +[
+  "airport_iata_code",
+  "schedule_type"
+]

changedInput schema / title

Previous value: -"flight_arrival_departure_scheduleArguments"New value: +"flight_arrival_departure_schedule_toolArguments"

changedOutput schema / title

Previous value: -"flight_arrival_departure_scheduleOutput"New value: +"flight_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 behavioral disclosure burden. It discloses the current-day-only limitation, optional airline filtering, and the per-flight fields returned. This is strong for a read-only schedule tool, though it does not discuss ordering or data availability.

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?

Two compact sentences with no filler: the core action and scope are front-loaded, followed by useful return-field details and the key routing to the future-date sibling.

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?

The description covers purpose, scope, key returned fields, and the critical date limitation. The schema fully documents parameters and the output schema covers return structure, so nothing essential is missing for correct invocation.

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 all four parameters are already documented. The description adds context by linking schedule_type to arrival/departure boards and mentioning airline_name filtering, but it does not add new syntax or format detail beyond the schema.

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 ('Return') and resource: today's arrival or departure board for an airport, with an optional airline filter. It also names the sibling future_flights_arrival_departure_schedule, making it easy to distinguish from the related tool.

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 scopes the tool to the current day and directs the agent to future_flights_arrival_departure_schedule for any later date. This gives clear when-to-use guidance and an explicit alternative, leaving no inference required.

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

Deploy Server