Skip to main content
Glama

Flat Flights — business & first class fares

Cheapest business class destinations from a city

cheapest_business_class_from
Read-only

Long-haul destinations from a departure city ranked by cheapest round-trip business class fare. Use for "where can I fly business class cheaply from X".

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

Input Schema

NameRequiredDescriptionDefault
fromYesCity name (e.g. "Milan", "New York") or 3-letter IATA city/airport code (e.g. "MIL", "JFK").
limitNo

Output Schema

NameRequiredDescriptionDefault
cityYes
pageYes
routesYes
fetchedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and open-world behavior are covered. The description adds useful context beyond that: results are ranked by cheapest round-trip business class fare and restricted to long-haul routes. It does not disclose fare recency, caching, currency, or whether the ranking is per-destination one-way/round-trip consistency, which matters for a price 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?

Two sentences, no filler, with the ranking definition front-loaded before the usage example. Every clause carries meaning. A tighter version would fold the directionality contrast into the first sentence rather than leaving it unspoken.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-value shape need not be explained, and the single required parameter is documented in the schema. The remaining gap is the undocumented 'limit' parameter and the absence of any note on fare freshness or result scope, which is modest but real for a two-parameter pricing tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: the 'from' parameter is well documented in the schema (city name or IATA code, max length) while 'limit' has no description anywhere. The description's word 'ranked' hints that the list is ordered and bounded, but it never explains what 'limit' controls, its default of 10, or the maximum of 50. With half the parameters undocumented, the description should have compensated and does not.

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 states a specific result type: long-haul destinations from a departure city ranked by cheapest round-trip business class fare. That is a clear verb+resource combination an agent can act on. It stops short of explicitly contrasting itself with the sibling 'cheapest_business_class_to', so the directionality is only inferred from the tool name and the phrase 'from a departure city'.

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 example query 'where can I fly business class cheaply from X' gives a clear intent match, which is real guidance. However, there is no exclusion or alternative routing — nothing tells the agent when to prefer 'cheapest_business_class_to' or 'business_class_deals', and no mention of fare freshness or coverage limits that would affect tool choice.

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