Check a flight connection
check_connectionAssess whether a flight connection leaves enough transfer time by deducting airport-specific steps from the layover and returning a comfort rating, reasons, and ticket-protection exposure.
Instructions
Assess whether a one-stop flight connection leaves enough time to transfer. Deducts the transfer steps that apply at the connection airport (walking, Schengen passport control, terminal change, security re-screening, baggage re-check) from the scheduled layover and returns comfortable / reasonable / tight / risky, the reasons, ticket-protection exposure, and the cited airport facts behind the estimate. Give the scheduled arrival and departure as local wall-clock times at the connection airport, or only layover_minutes when that is all the user said. Explain the result using the returned steps; airport facts are context and only apply where their scope matches the trip. To compare two or more options, call compare_connections once instead of this tool for each.
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": {
"from": "<from>",
"via": "<via>",
"to": "<to>"
},
"name": "check_connection"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | Destination airport of the second flight (IATA), e.g. PVG | |
| via | Yes | Connection airport (IATA), e.g. IST | |
| from | Yes | Origin airport of the first flight (IATA), e.g. BER | |
| ticket | No | protected = both flights on one ticket/booking; separate = self-transfer on separate tickets; unknown if not stated | unknown |
| arrival_time | No | Scheduled arrival of the first flight at the connection airport, local time, YYYY-MM-DDTHH:mm. Give both times, or layover_minutes instead. | |
| departure_time | No | Scheduled departure of the second flight from the connection airport, local time, YYYY-MM-DDTHH:mm. Give both times, or layover_minutes instead. | |
| baggage_recheck | No | true if checked bags must be collected and checked in again, false if not (hand luggage only, or bags checked through). On separate tickets, leave it out only if unknown: the result then says whether it matters. | |
| layover_minutes | No | Scheduled time between arrival and departure, in minutes. Use this when the user gives only a layover duration; do not invent dates or clock times. | |
| terminal_change | No | Set true if a terminal change is known but terminals are not given | |
| arrival_terminal | No | Arrival terminal at the connection airport, if known | |
| departure_terminal | No | Departure terminal at the connection airport, if known |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| route | Yes | ||
| steps | Yes | ||
| ticket | Yes | ||
| factors | Yes | ||
| quality | Yes | ||
| verdict | Yes | ||
| decision | Yes | What to do with this connection. insufficient_data means key information is missing: ask the user rather than recommending it. | |
| confidence | Yes | How far the estimate can be trusted, independent of the quality rating. Low means key information is missing. | |
| disclaimer | Yes | ||
| layover_basis | Yes | How the layover length was computed: the airport's time zone, explicit UTC offsets, plain clock difference, or a given duration. | |
| buffer_minutes | Yes | ||
| layover_source | Yes | ||
| baggage_recheck | Yes | ||
| layover_minutes | Yes | ||
| connection_airport | Yes | ||
| if_baggage_recheck | No | Separate tickets with unknown bags: the result if bags must be re-checked. | |
| transfer_process_minutes | Yes | ||
| wall_clock_layover_minutes | No | Present when clocks change during the layover: what the local clocks show. |