Skip to main content
Glama

flight_arrival_departure_schedule

Retrieve today's arrival or departure board for an airport, optionally filtered by airline, with flight times, terminals, gates, and departure 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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "airport_iata_code": "<airport_iata_code>",
      "schedule_type": "<schedule_type>"
    },
    "name": "flight_arrival_departure_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
airline_nameNoOptional airline name filter.
schedule_typeYesWhether to return the arrival board or the departure board. One of: arrival, departure.
airport_iata_codeYesAirport IATA code (for example: SFO).
number_of_flightsNoMaximum number of flights to return, from 1 to 100.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.1

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.