Skip to main content
Glama

Search flight fares for a route and date, with nonstop options

flights
Read-only

Flight fares for one route and date, one-way or round trip: the cheapest, the fastest and the cheapest nonstop option, then up to 20 itineraries sorted by price with carrier, stops, duration, departure and arrival times (local and UTC), every flight segment and aircraft. Cabin, maximum stops and market (sets the currency) are optional. Fares for a single traveller from Ignav; a fare search, not a booking. Price: $0.05 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
toYesArrival airport, 3-letter IATA code, e.g. LHR
dateYesDeparture date YYYY-MM-DD (today to 330 days ahead)
fromYesDeparture airport, 3-letter IATA code, e.g. IST
cabinNoeconomy (default), premium_economy, business or first
limitNoItineraries to return, 1-20, default 10
marketNo2-letter country code that sets the currency, default US (USD); e.g. GB, DE, TR
returnNoReturn date YYYY-MM-DD for a round trip (optional)
maxStopsNoMaximum stops per direction: 0, 1, 2 or 3 (optional)

Output Schema

NameRequiredDescriptionDefault
noteNo
countNo
queryNo
sourceNo
fastestNo
cheapestNo
currencyNo
checkedAtNo
observedAtNo
itinerariesNo
cheapestNonstopNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnly and openWorld; the description goes well beyond them by disclosing the data source (Ignav), the commercial model ($0.05 per successful call via x402/USDC on Base and other networks), and crucially that failed calls are not charged. It also scopes results to a single traveller and clarifies no booking occurs.

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?

The content is front-loaded with the resource and output shape, and the trailing clauses about pricing and non-booking status are genuinely load-bearing. It reads as one long run-on sentence, but almost every clause adds decision-relevant information rather than filler.

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

Completeness5/5

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

All the elements an agent needs are present: complete parameter coverage in the schema, annotations for safety and openness, a rich output schema for return values, and description-level disclosure of cost, billing mechanism, and result cardinality. Nothing material is left to inference.

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 100%, so all eight parameters are already documented by the schema itself. The description restates optionality and adds only marginal meaning, mainly that 'return' turns a one-way into a round trip and that market determines currency. One useful detail not in the schema is that up to 20 itineraries are returned sorted by price.

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 and resource ('flight fares for one route and date') and enumerates the exact return shape (cheapest, fastest, cheapest nonstop, then up to 20 itineraries). It also disambiguates scope with 'a fare search, not a booking', distinguishing it from an airport-lookup or booking sibling.

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?

It states the required inputs implicitly (one route and one date), which optional knobs exist (cabin, max stops, market), and that it is oriented to a single traveller. What is missing is explicit routing guidance, e.g. that airport codes can be resolved via the 'airports' sibling before calling this.

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