Skip to main content
Glama

Luxury Travel Tools by Global Lux Agency

Flight Arrival Time Calculator

flight-arrival-time-calculator
Read-onlyIdempotent

Converts a local departure time and a journey time into the local arrival date and time at the destination, using IANA time-zone rules (including daylight saving on the exact dates). Alternatively, pass the local arrival time to get the journey time. Returns the time difference when landing (which can exceed 12 hours across the date line), the calendar-day change as airlines show it (+1, +2, −1), a plain-English explanation and any clock-change notes. Does not look up flights or schedules. Web page: https://globalluxagency.com/tools/flight-arrival-time-calculator

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": {
      "departureTimeZone": "<departureTimeZone>",
      "arrivalTimeZone": "<arrivalTimeZone>",
      "departure": "<departure>"
    },
    "name": "flight-arrival-time-calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
arrivalNoOptional: arrival, local time at the destination, YYYY-MM-DDTHH:MM. If given, the journey time is worked out from it.
departureYesDeparture, local time at the departure airport, YYYY-MM-DDTHH:MM.
flightHoursNoJourney time, whole hours (use with flightMinutes). Ignored if arrival is given.
flightMinutesNoJourney time, extra minutes (0–59).
arrivalTimeZoneYesIANA time zone of the arrival airport, e.g. Pacific/Honolulu.
departureTimeZoneYesIANA time zone of the departure airport, e.g. Pacific/Auckland.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, closed-world behavior, and the description adds substantive context beyond them: DST is applied to the exact dates, results include elapsed time (which may exceed 12 hours across the date line), airline-style day change (+1, +2, −1), a plain-English explanation and clock-change notes. Since no output schema exists, this disclosure of return contents is genuinely load-bearing.

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?

Front-loaded with the primary conversion, then the alternate mode, then return contents, then scope exclusion — a logical ordering with no filler. The trailing web-page URL is mildly extraneous for agent use but does not obscure the content.

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?

A six-parameter calculator with no output schema needs the description to explain both input modes and what comes back; it does exactly that, covering elapsed time, day offset, explanation and clock changes. Nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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, but the description adds the conditional relationship between parameters ('Alternatively, pass the local arrival time to get the journey time') that tells an agent the two input modes are mutually exclusive. It also notes IANA time-zone rules, which reinforces the format expected by the zone parameters.

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 ('Converts a local departure time and a journey time into the local arrival date and time at the destination'), names the inverse mode, and explicitly scopes out non-goals ('Does not look up flights or schedules'). An agent can distinguish this from unrelated sibling calculators like jet-lag-planner without opening the schema.

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

Usage Guidelines4/5

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

Gives clear guidance on both operating modes: supply journey time forward, or 'pass the local arrival time to get the journey time' backward, plus the exclusion that it does not query flight data. It does not name an alternative tool, but none of the listed siblings plausibly overlap, so the gap is minor.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources