Skip to main content
Glama

Cheapest routes

cheapest_routes
Read-only

Use this when someone asks where they can fly cheaply from a city, or for flight deals under a budget or in a month. Returns the cheapest fare on each route with fares from an origin (or into a destination), cheapest one-way first, each with its cheapest round trip of a 3 to 21 day stay in return when the route has one. Filter by a maximum price and a departure month here rather than by reading the list; both apply to the one-way. Prices are for one adult in economy; each fare carries found_at, the day it was found (or checked, the day its route was last checked, when it has none), and a one-way may carry typical_price and pct_below_typical.

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

Input Schema

NameRequiredDescriptionDefault
toNowhere the flights land: destination IATA airport or city code
fromNowhere the flights leave from: origin IATA airport or city code (NYC covers JFK, LGA and EWR); give from, to or both
limitNohow many routes to return, 1 to 20; 10 when omitted
monthNoYYYY-MM: the cheapest fare departing in that month; needs from
max_priceNokeep only fares at or under this amount, in the currency the results carry

Output Schema

NameRequiredDescriptionDefault
noteNo
routesYes
currencyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changed
    • changedOutput schema / properties / routes / items / properties / book_url / description
      Previous value: -"opens the seller's booking page for this fare"New value: +"opens the seller's booking page for this fare, where the final price and bag fees appear at checkout"
    • changedOutput schema / properties / routes / items / properties / checked / description
      Previous value: -"the day we last checked this route — not the day the price was seen, which can be days earlier"New value: +"YYYY-MM-DD: the day this route was last checked; found_at, when present, is the day this fare was found"
    • addedOutput schema / properties / routes / items / properties / found_at
      Added value: +{
      +  "description": "YYYY-MM-DD: the day this fare was found; absent when only checked is known",
      +  "type": "string"
      +}
    • addedOutput schema / properties / routes / items / properties / pct_below_typical
      Added value: +{
      +  "description": "one-way only: how many percent this fare is under typical_price; present only when 10 or more",
      +  "type": "integer"
      +}
    • changedOutput schema / properties / routes / items / properties / return / description
      Previous value: -"the route's cheapest round trip of a 3 to 21 day stay; absent when we hold none, and the route's page_url then offers a live return search"New value: +"the route's cheapest round trip of a 3 to 21 day stay; absent when the route has none, and the route's page_url then offers a return search"
    • changedOutput schema / properties / routes / items / properties / return / properties / book_url / description
      Previous value: -"opens the seller's booking page for this fare"New value: +"opens the seller's booking page for this fare, where the final price and bag fees appear at checkout"
    • changedOutput schema / properties / routes / items / properties / return / properties / checked / description
      Previous value: -"the day we last checked this route — not the day the price was seen, which can be days earlier"New value: +"YYYY-MM-DD: the day this route was last checked; found_at, when present, is the day this fare was found"
    • addedOutput schema / properties / routes / items / properties / return / properties / found_at
      Added value: +{
      +  "description": "YYYY-MM-DD: the day this fare was found; absent when only checked is known",
      +  "type": "string"
      +}
    • addedOutput schema / properties / routes / items / properties / return / properties / pct_below_typical
      Added value: +{
      +  "description": "one-way only: how many percent this fare is under typical_price; present only when 10 or more",
      +  "type": "integer"
      +}
    • removedOutput schema / properties / routes / items / properties / return / properties / seen
      Removed value: -{
      -  "description": "the day this price was seen; absent when we know only the day we last checked it",
      -  "type": "string"
      -}
    • addedOutput schema / properties / routes / items / properties / return / properties / typical_price
      Added value: +{
      +  "description": "one-way only: the route's typical one-way fare, the median of each departure date's cheapest one-way, in currency",
      +  "type": "number"
      +}
    • removedOutput schema / properties / routes / items / properties / seen
      Removed value: -{
      -  "description": "the day this price was seen; absent when we know only the day we last checked it",
      -  "type": "string"
      -}
    • addedOutput schema / properties / routes / items / properties / typical_price
      Added value: +{
      +  "description": "one-way only: the route's typical one-way fare, the median of each departure date's cheapest one-way, in currency",
      +  "type": "number"
      +}
  2. Changed2 schema fields changed
    • changedInput schema / properties / from / description
      Previous value: -"origin IATA airport or city code (NYC covers JFK, LGA and EWR); give from, to or both"New value: +"where the flights leave from: origin IATA airport or city code (NYC covers JFK, LGA and EWR); give from, to or both"
    • changedInput schema / properties / to / description
      Previous value: -"destination IATA airport or city code"New value: +"where the flights land: destination IATA airport or city code"
  3. Changed4 schema fields changed
    • changedOutput schema / properties / routes / items / properties / checked / description
      Previous value: -"the day this price was last seen"New value: +"the day we last checked this route — not the day the price was seen, which can be days earlier"
    • changedOutput schema / properties / routes / items / properties / return / properties / checked / description
      Previous value: -"the day this price was last seen"New value: +"the day we last checked this route — not the day the price was seen, which can be days earlier"
    • addedOutput schema / properties / routes / items / properties / return / properties / seen
      Added value: +{
      +  "description": "the day this price was seen; absent when we know only the day we last checked it",
      +  "type": "string"
      +}
    • addedOutput schema / properties / routes / items / properties / seen
      Added value: +{
      +  "description": "the day this price was seen; absent when we know only the day we last checked it",
      +  "type": "string"
      +}
  4. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already establish that this is a safe, read-only operation. The description adds meaningful behavior beyond them: the prices are for one adult in economy, the results are ordered cheapest one-way first, each returned route may include a cheapest round trip based on a 3–21 day stay, and it explains the found_at, typical_price, and pct_below_typical fields. This is solid, though it does not cover data freshness or currency beyond a brief mention.

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 definition opens with the use case, then describes what is returned and how the filters behave. Only one dense paragraph is used, and nearly every clause carries information, though the fare-field enumeration is slightly compressed and hard to parse in one pass.

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 the description does not need to define return values, yet it explains the key fare semantics anyway. It covers the tool's direction options, the filtering rules, and the ordering. The remaining gap is that it never routes the agent to route_fares or explains when to choose that tool instead.

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

Parameters4/5

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

Schema description coverage is 100%, so the schema already documents all five parameters. The description still adds non-obvious meaning: max_price and month filter the one-way fare, not the round trip, which an agent could easily get wrong. It also restates that month only works with a departure month paired with an origin.

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 uses a specific verb and resource: it returns the cheapest fare on each route, from an origin or into a destination, with the cheapest one-way first. It communicates scope precisely enough to separate a directional cheap-fare lookup from a generic fare lookup. It makes no mention of individual sibling tools such as route_fares, so sibling differentiation is implied rather than stated.

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 clearly states when to use the tool: when someone asks where they can fly cheaply from a city, or asks for deals under a budget or in a given month. It also tells the agent to filter by max_price and month here rather than reading the whole list. No alternative sibling tool is named for the other cases, which is the only gap.

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