Skip to main content
Glama

Luxury Travel Tools by Global Lux Agency

Jet Lag Planner

jet-lag-planner
Read-onlyIdempotent

Builds a jet lag plan from the home and destination time zones, the flight’s local departure and arrival times and the traveller’s usual sleep. Returns the body-clock shift needed, the direction (advance or delay), and for each day before departure, the travel day and the days after arrival: a sleep window, light to seek, light to avoid and an optional caffeine cut-off. Based on published circadian research; general guidance, not medical advice. Web page: https://globalluxagency.com/tools/jet-lag-planner

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": {
      "homeTimeZone": "<homeTimeZone>",
      "destinationTimeZone": "<destinationTimeZone>",
      "departure": "<departure>",
      "arrival": "<arrival>"
    },
    "name": "jet-lag-planner"
  }
}

Input Schema

NameRequiredDescriptionDefault
arrivalYesArrival, local time at the destination, YYYY-MM-DDTHH:MM.
bedtimeNoUsual bedtime at home, HH:MM (24-hour).23:00
caffeineNoInclude a daily caffeine cut-off.
strategyNoShift the body clock earlier (advance), later (delay), or let the planner choose (auto).auto
wakeTimeNoUsual wake time at home, HH:MM (24-hour).07:00
departureYesDeparture, local time at home, YYYY-MM-DDTHH:MM.
homeTimeZoneYesIANA time zone at home, e.g. Europe/London.
preflightDaysNoDays before departure to start shifting sleep (0 = none; 2–3 suggested).
destinationTimeZoneYesIANA time zone at the destination, e.g. Asia/Dubai.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the output is a deterministic circadian computation grounded in 'published circadian research', it returns a day-by-day schedule spanning pre-flight, travel day and post-arrival days, and it carries a not-medical-advice disclaimer. No cost, latency or failure modes are mentioned, which keeps it short of a 5.

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?

Structure is front-loaded and logical: purpose first, then inputs, then outputs, then caveat, then link. The long middle sentence is dense but every clause carries information an agent needs. The trailing marketing URL is the only element that does not strictly earn its place, and the medical disclaimer could be trimmed.

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?

There is no output schema, so the description must carry the return contract, and it does so reasonably well by listing the shift, direction and per-day advice categories. With nine fully documented parameters and a complete annotation set, the only residual gap is the shape of the result (flat list vs. grouped phases, how days are labeled). For a stateless pure-computation tool that is a minor omission.

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 every one of the nine parameters (including defaults for bedtime, wakeTime, preflightDays, strategy and caffeine) is already documented in the schema with formats and examples. The description restates the key inputs at a high level but adds no format, constraint or interaction detail beyond what the schema provides. Baseline 3 is the correct landing point when the schema does the heavy lifting.

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?

The description opens with a specific verb and resource ('Builds a jet lag plan') and immediately names the inputs that drive it (home/destination time zones, local departure and arrival times, usual sleep). It goes further to enumerate the outputs (body-clock shift, direction, per-day sleep window, light to seek/avoid, caffeine cut-off), so an agent knows exactly what it gets back. The sibling tools are all finance/regulation calculators, so no disambiguation is needed and none is wasted.

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

Usage Guidelines3/5

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

Usage is only implied: the input list makes clear it applies to a flight between two time zones with a known sleep schedule. There is no explicit when-to-use statement, no prerequisites (e.g. that departure and arrival must be in different local zones), and no named alternative for related questions. The 'general guidance, not medical advice' caveat is a scope boundary rather than tool-selection guidance.

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