Skip to main content
Glama

Flat Flights — business & first class fares

Cheaper nearby departure cities (positioning flights) for Business & First Class

compare_departure_hubs
Read-only

Business class & First class positioning comparison: checks nearby and same-country departure airports/cities to the same destination to find €500–€2,500+ savings (e.g. flying from Milan, Dublin, Warsaw or Madrid instead of London, Zurich or Frankfurt).

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": "compare_departure_hubs"
  }
}

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

Output Schema

NameRequiredDescriptionDefault
cabinNo
destinationYes
directRouteNo
alternativesYes
originRequestedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description's job is to add context; it does clarify the search breadth ('nearby and same-country' departure airports rather than a fixed origin) and the expected savings magnitude. It does not disclose whether results are live-priced, what currency the comparison is in (the € ranges hint at EUR only), or how many alternative hubs are scanned.

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?

One front-loaded sentence that names the operation first and the payoff second, with parenthetical examples that clarify the concept quickly. The '€500–€2,500+ savings' figure is slightly promotional, but it is short and does convey the value proposition.

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 an output schema, annotations, and documented params, the description only needs to convey the comparison concept and scope, which it does. Minor gaps remain around currency/live pricing and how the results should be interpreted, but nothing essential to invoking the tool 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 67% and both from/to are documented with format examples plus the cabin enum with its default, so the structured fields carry the parameter burden. The description adds no additional meaning about how from is treated (origin vs. home market) or how cabin interacts with the comparison, so it stays at the baseline.

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?

States a specific action (compare departure airports/cities for the same destination) and a specific resource scope (nearby and same-country positioning for Business/First), with concrete example city pairs. The 'not from your home airport' angle implicitly separates it from siblings like cheapest_business_class_from or check_business_or_first_price, though no sibling is named.

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: an agent can infer it should call this when considering alternative departure cities to save money, but there is no explicit 'use when' statement, no prerequisites, and no named alternative tool for the case where the user wants a fixed departure airport.

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