Skip to main content
Glama

Flat Flights — business & first class fares

Verify real-time bookable Business/First Class flights, aircraft & direct checkout cart

verify_live_flight_offers
Read-only

Real-time flight verification (~8 seconds): queries airlines and OTAs live for exact dates to confirm bookable EUR prices right now, operating airlines, flight numbers, widebody vs narrowbody aircraft on each leg, and a directCheckoutLink that opens the airline or OTA booking cart directly. Call this when the user is ready to verify or book specific dates.

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>",
      "depart_date": "<depart_date>"
    },
    "name": "verify_live_flight_offers"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesCity name (e.g. "Milan", "New York") or 3-letter IATA city/airport code (e.g. "MIL", "JFK").
fromYesCity name (e.g. "Milan", "New York") or 3-letter IATA city/airport code (e.g. "MIL", "JFK").
cabinNobusiness
adultsNo
depart_dateYesOutbound date (YYYY-MM-DD, today to 330 days ahead).
return_dateNoReturn date; omit for one way (YYYY-MM-DD, today to 330 days ahead). Optional: the booking link then opens the search on the traveller's dates instead of the quoted fare's.

Output Schema

NameRequiredDescriptionDefault
noteNo
cabinNo
adultsNo
offersYes
originNo
statusYes
departDateNo
returnDateNo
verifiedAtNo
destinationNo
offersCountNo
aviasalesSearchLinkYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / status / enum
      Previous value: -[
      -  "ok",
      -  "no_offers",
      -  "unavailable"
      -]New value: +[
      +  "ok",
      +  "no_offers",
      +  "archive_fallback",
      +  "unavailable"
      +]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description earns credit for adding beyond them: an ~8 second latency figure, the fact that live airline/OTA systems are queried, and that directCheckoutLink opens an external booking cart. It stops short of covering failure modes or what happens when no bookable fare is found.

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, front-loaded with the core action and latency, followed by a single crisp usage trigger. Every clause adds information and nothing is repeated from the schema or annotations.

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 annotations and an output schema already supplied, the description covers what is verified, how fresh it is, how long it takes, and when to call it. Remaining gaps are minor: no mention of empty-result behavior and no acknowledgement that the cabin parameter includes premium beyond Business/First.

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 67% and the schema itself carries the detailed parameter explanations (city name vs IATA code, date window, return_date's effect on the booking link). The prose only reinforces the "exact dates" framing and does not explain the cabin enum, which includes "premium" despite the Business/First framing, nor adults limits.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb+resource ("queries airlines and OTAs live") and enumerates exactly what is verified: EUR prices, operating airlines, flight numbers, widebody vs narrowbody per leg, and a directCheckoutLink. It implicitly separates itself from the sibling search/deal tools via "real-time" and "right now", but it never names an alternative, so it falls short of full sibling differentiation.

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?

"Call this when the user is ready to verify or book specific dates" gives a clear readiness condition that implicitly distinguishes it from browse/search siblings. It does not state when NOT to use it (e.g. flexible dates) or name a fallback tool, so no explicit exclusions are present.

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