Skip to main content
Glama

Check a hidden-city ticket

check_hidden_city_ticket
Read-only

Assess the risk of hidden-city ticketing: buying a ticket to a farther airport and getting off at the layover. Returns the saving, a verdict, deal-breakers, risks and the airline's policy.

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>",
      "to": "<to>",
      "beyond": "<beyond>",
      "direct": "<direct>",
      "throwaway": "<throwaway>"
    },
    "name": "check_hidden_city_ticket"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesHub airport where you would actually get off, e.g. LHR
bagNoTrue if you would check a bag
fromYesOrigin airport IATA code, e.g. JFK
beyondYesFinal airport on the cheaper ticket, e.g. DUB, EDI, MAN, BRU, AMS for LHR
directYesPrice of the normal ticket to your real destination, USD
airlineNoAirline code. Defaults to IZ (other).
loyaltyNoTrue if a frequent flyer number is on the booking
throwawayYesPrice of the cheaper ticket to the airport beyond, USD
round_tripNoTrue if the ticket is a return

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / beyond / description
      Previous value: -"Final airport on the cheaper ticket, e.g. DUB"New value: +"Final airport on the cheaper ticket, e.g. DUB, EDI, MAN, BRU, AMS for LHR"
    • addedInput schema / properties / from / enum
      Added value: +[
      +  "JFK",
      +  "EWR",
      +  "LAX",
      +  "SFO",
      +  "ORD",
      +  "MIA",
      +  "BOS",
      +  "IAD",
      +  "IAH",
      +  "DFW",
      +  "ATL",
      +  "SEA",
      +  "DEN",
      +  "PHX",
      +  "MSP",
      +  "LHR",
      +  "CDG",
      +  "FCO",
      +  "BCN",
      +  "MAD",
      +  "AMS",
      +  "FRA",
      +  "DUB",
      +  "LIS",
      +  "ATH",
      +  "IST",
      +  "KEF",
      +  "NRT",
      +  "HND",
      +  "ICN",
      +  "SIN",
      +  "HKG",
      +  "BKK",
      +  "TPE",
      +  "DEL",
      +  "SYD",
      +  "DOH",
      +  "DXB",
      +  "GRU",
      +  "BOG",
      +  "LIM",
      +  "SCL",
      +  "MEX",
      +  "CUN"
      +]
    • changedInput schema / properties / to / description
      Previous value: -"Airport where you would actually get off, e.g. LHR"New value: +"Hub airport where you would actually get off, e.g. LHR"
    • addedInput schema / properties / to / enum
      Added value: +[
      +  "LHR",
      +  "CDG",
      +  "FRA",
      +  "AMS",
      +  "FCO",
      +  "MAD",
      +  "BCN",
      +  "IST",
      +  "DXB",
      +  "DOH",
      +  "NRT",
      +  "HND",
      +  "ICN",
      +  "SIN",
      +  "HKG",
      +  "BKK",
      +  "DEL",
      +  "GRU",
      +  "SYD"
      +]
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description goes beyond that by enumerating the computed outputs (saving, verdict, deal-breakers, risks, airline policy), which is genuinely useful because no output schema exists. It does not mention cost, latency or any limits, so it stops 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no filler: the first gives the purpose and definition, the second lists the return payload. The most important information (what is being assessed) is front-loaded.

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?

With nine parameters, no output schema and safety annotations already present, the description covers the two things that matter most: what is computed and what comes back. It is complete enough to invoke correctly, though a note on how to interpret the verdict or on deal-breaker inputs would make it fully self-contained.

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% and all nine parameters (from, to, beyond, direct, throwaway, bag, airline, loyalty, round_trip) carry inline descriptions with examples, so the schema does the heavy lifting. The description adds no parameter-level meaning beyond hinting that airline policy is factored in, which is the baseline 3 for a fully documented 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 and resource ('Assess the risk of hidden-city ticketing') and immediately defines the concept it evaluates ('buying a ticket to a farther airport and getting off at the layover'). This is clearly distinct from the sibling tools get_latest_deals, open_friday_flight_deals and score_flight_deal, which deal with deals and generic deal scoring rather than the hidden-city risk model.

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?

The description implies the scenario in which the tool applies (a traveler considering an intentional hidden-city itinerary) but never says when to prefer it over score_flight_deal or what prerequisites exist. Usage is inferable from the scenario framing rather than stated, which is the textbook 'implied usage' case.

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