Skip to main content
Glama

Flat Flights — business & first class fares

Cheapest First Class flights on long-haul routes

first_class_fares
Read-only

First Class suites & flagship cabins (trip_class=2) round-trip fares on long-haul routes from Aviasales data, ranked cheapest first, with First Class booking links. Optional from filters to one departure city.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "first_class_fares"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
pageYes
routesYes
fetchedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered and the bar is lower. The description still adds real behavior beyond them: results come from Aviasales, are restricted to round-trip long-haul itineraries, are sorted cheapest first, and include booking links. It omits currency, pricing freshness, and whether the links are affiliate/booking-partner links.

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 compact sentences, no filler. The scope and cabin qualifier are front-loaded, and the parameter note is placed last where it does not interrupt the core statement of purpose.

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?

An output schema exists, so return values need not be explained. For a two-parameter, no-required-parameter search tool, the description covers cabin, route type, ordering, source, links, and the optional filter well. Minor gaps are currency and the default scope when `from` is omitted (all origins vs. a default hub).

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 exactly 50%: `from` is fully documented in the schema, while `limit` has no description anywhere. The description clarifies that `from` is optional and narrows results to a single departure city (implying all departure cities otherwise), which is useful disambiguation, but it says nothing about `limit` or the result cap.

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 names the specific resource (round-trip First Class / trip_class=2 fares on long-haul routes), the data source (Aviasales), the ordering (cheapest first), and the output extras (First Class booking links). It implicitly separates itself from the business-class siblings by scoping strictly to First Class, though it never explicitly names an alternative tool.

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 agent can infer this is the tool for First Class long-haul fares and that the business-class siblings cover the other cabin. There is no explicit when-to-use/when-not statement and no mention of when `check_business_or_first_price` or `cash_vs_miles_options` would be preferable.

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