Skip to main content
Glama
open-transfer-times

open-transfer-times

Check a flight connection

check_connection
Read-onlyIdempotent

Assess 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

NameRequiredDescriptionDefault
toYesDestination airport of the second flight (IATA), e.g. PVG
viaYesConnection airport (IATA), e.g. IST
fromYesOrigin airport of the first flight (IATA), e.g. BER
ticketNoprotected = both flights on one ticket/booking; separate = self-transfer on separate tickets; unknown if not statedunknown
arrival_timeNoScheduled arrival of the first flight at the connection airport, local time, YYYY-MM-DDTHH:mm. Give both times, or layover_minutes instead.
departure_timeNoScheduled departure of the second flight from the connection airport, local time, YYYY-MM-DDTHH:mm. Give both times, or layover_minutes instead.
baggage_recheckNotrue 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_minutesNoScheduled 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_changeNoSet true if a terminal change is known but terminals are not given
arrival_terminalNoArrival terminal at the connection airport, if known
departure_terminalNoDeparture terminal at the connection airport, if known

Output Schema

NameRequiredDescriptionDefault
routeYes
stepsYes
ticketYes
factorsYes
qualityYes
verdictYes
decisionYesWhat to do with this connection. insufficient_data means key information is missing: ask the user rather than recommending it.
confidenceYesHow far the estimate can be trusted, independent of the quality rating. Low means key information is missing.
disclaimerYes
layover_basisYesHow the layover length was computed: the airport's time zone, explicit UTC offsets, plain clock difference, or a given duration.
buffer_minutesYes
layover_sourceYes
baggage_recheckYes
layover_minutesYes
connection_airportYes
if_baggage_recheckNoSeparate tickets with unknown bags: the result if bags must be re-checked.
transfer_process_minutesYes
wall_clock_layover_minutesNoPresent when clocks change during the layover: what the local clocks show.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.2.1
    • changedInput schema / properties / arrival_time / pattern
      Previous value: -"^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}(:\\d{2})?$"New value: +"^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}(:\\d{2})?(Z|[+-]\\d{2}:\\d{2})?$"
    • changedInput schema / properties / baggage_recheck / description
      Previous value: -"Set true if checked bags must be collected and checked in again"New value: +"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."
    • changedInput schema / properties / departure_time / pattern
      Previous value: -"^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}(:\\d{2})?$"New value: +"^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}(:\\d{2})?(Z|[+-]\\d{2}:\\d{2})?$"
    • addedOutput schema / properties / baggage_recheck
      Added value: +{
      +  "enum": [
      +    "required",
      +    "not_required",
      +    "unknown"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / decision
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "What to do with this connection. insufficient_data means key information is missing: ask the user rather than recommending it.",
      +  "properties": {
      +    "reasons": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "code": {
      +            "type": "string"
      +          },
      +          "explanation": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "code",
      +          "explanation"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "value": {
      +      "enum": [
      +        "recommend",
      +        "caution",
      +        "insufficient_data",
      +        "avoid"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "value",
      +    "reasons"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / if_baggage_recheck
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Separate tickets with unknown bags: the result if bags must be re-checked.",
      +  "properties": {
      +    "buffer_minutes": {
      +      "type": "number"
      +    },
      +    "quality": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "buffer_minutes",
      +    "quality"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / layover_basis
      Added value: +{
      +  "description": "How the layover length was computed: the airport's time zone, explicit UTC offsets, plain clock difference, or a given duration.",
      +  "enum": [
      +    "timezone",
      +    "offset",
      +    "wall_clock",
      +    "duration"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / wall_clock_layover_minutes
      Added value: +{
      +  "description": "Present when clocks change during the layover: what the local clocks show.",
      +  "type": "number"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "route",
      -  "layover_source",
      -  "quality",
      -  "verdict",
      -  "layover_minutes",
      -  "transfer_process_minutes",
      -  "buffer_minutes",
      -  "steps",
      -  "factors",
      -  "confidence",
      -  "ticket",
      -  "connection_airport",
      -  "disclaimer"
      -]New value: +[
      +  "route",
      +  "layover_source",
      +  "decision",
      +  "layover_basis",
      +  "baggage_recheck",
      +  "quality",
      +  "verdict",
      +  "layover_minutes",
      +  "transfer_process_minutes",
      +  "buffer_minutes",
      +  "steps",
      +  "factors",
      +  "confidence",
      +  "ticket",
      +  "connection_airport",
      +  "disclaimer"
      +]
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds real substance: the deduction model (walking, passport control, terminal change, security, bag re-check), the output categories (comfortable/reasonable/tight/risky), and ticket-protection exposure. It does not discuss latency or data-freshness of the cited airport facts, which would have pushed it higher.

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?

Purpose is front-loaded and the parenthetical step list earns its place by explaining how the estimate is built. The final sentences on interpreting results are dense but not padded; a shorter split into distinct sentences would read more cleanly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers the 11-parameter surface with its two input modes, names the decision categories, and points to the alternative tool; an output schema exists so return values need not be spelled out. Minor gap: nothing says how the tool behaves when both time fields and layover_minutes are supplied.

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 baseline is 3. The description reinforces the times-vs-layover_minutes trade-off and the meaning of ticket protection, but adds little format or edge-case detail beyond what the schema descriptions already say.

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 ('Assess whether a one-stop flight connection leaves enough time to transfer') and immediately differentiates from the sibling by naming compare_connections for multi-option comparisons.

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?

Explicit routing: use compare_connections once for two or more options rather than calling this per option. Also gives input-mode guidance (give both local wall-clock times, or only layover_minutes when that is all the user said) and warns that airport facts apply only where scope matches.

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