Skip to main content
Glama

Flat Flights — business & first class fares

Business class fares between two cities

search_business_class_fares
Read-only

Cheapest round-trip business class fare between two cities, with dates, stops, cheapest departure month, cheapest nonstop and one-way fares, nonstop flights seen (airline, flight, airports), a lie-flat assessment and a booking link that opens a search on the quoted fare's dates (or the traveller's dates, if given).

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

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").
adultsNoAdults for the booking link search.
depart_dateNoOutbound date (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.
return_dateNoReturn date; omit with depart_date 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
pageNo
faresNo
foundYes
routeNo
originNo
reasonNo
fetchedAtNo
requestedNoPresent when depart_date was passed: how the fares seen compare with the traveller's dates.
originNameNo
bookingLinkNo
destinationNo
bookingSearchNoWhat bookingLink opens: site, dates (null = about two weeks ahead) and adults.
destinationNameNo

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 and openWorldHint, so the safety profile is covered. The description adds real behavioral context beyond that: the response includes a lie-flat assessment, a cheapest departure month, and a booking link whose date behavior flips between the quoted fare's dates and the traveller's dates. It does not mention freshness/caching or rate limits for a live-search tool.

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?

It is a single sentence with the core purpose front-loaded before the enumeration of return fields, and no filler words. The trailing list of outputs is long and partly redundant given an output schema exists, which keeps it from a 5.

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?

For a five-parameter read-only search with full schema coverage and an output schema, the description supplies everything an agent needs to invoke it correctly, including the optional-date behavior. It is slightly over-complete on return fields, which the output schema already covers, but nothing essential is missing.

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 schema already documents every parameter, including the depart_date/return_date booking-link interaction. The description restates that link behavior at a high level but adds no new syntax, format, or constraint information beyond the schema, so the baseline of 3 applies.

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 names a specific verb-plus-resource: cheapest round-trip business class fare between two cities. The qualifiers 'round-trip', 'business class' and 'between two cities' distinguish it from first_class_fares and the directional cheapest_business_class_from/to siblings without needing to name them.

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 word 'round-trip' and the presence of optional dates signal a round-trip fare search, and the one-way fares being included is mentioned in passing. There is no explicit statement of when to prefer this over business_class_deals, cheapest_business_class_from/to, or compare_departure_hubs, and no exclusions or prerequisites.

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