Skip to main content
Glama

One-way flight options with prices from Google Flights

travel_google_flights
Read-only

One-way flight options with prices from Google Flights for a route and date (IATA codes, e.g. JFK to LHR): lowest fare in USD, airline(s), stops, departure and arrival airport, local times and dates, total duration and layover airports, as shown on Google's public results page. Economy, 1 adult. Prices change constantly and are Google's displayed 'from' fares, not bookings. Related tools on this server, for a different need: travel_google_hotels_price when you need lowest nightly hotel prices for a city and stay dates; travel_google_travel when you need Google Travel hotels and vacation rentals for a place. Price: $0.002 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": "travel_google_flights"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesDestination airport or city IATA code, e.g. LHR, LON (required)
dateYesDeparture date YYYY-MM-DD, today or later (required)
fromYesOrigin airport or city IATA code, e.g. JFK, NYC (required)
limitNoFlights to return, 1 to 50 (default 20)
nonstopOnlyNotrue to keep only nonstop flights

Output Schema

NameRequiredDescriptionDefault
toNo
dateNo
fromNo
countNo
totalNo
sourceNo
flightsNo
cheapestNo
checkedAtNo
nonstopOnlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantial context beyond them: results are Google's displayed 'from' fares and are not bookings, prices change constantly, the query is fixed to Economy/1 adult, and the call is metered at $0.002 per successful call via x402 with failures not charged. Cost and billing-rail disclosure is exactly the kind of information annotations cannot carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded correctly, with the purpose and fixed assumptions before the sibling routing and pricing. However, the long enumeration of return fields (fare, airlines, stops, airports, times, duration, layovers) partly duplicates the published output schema, and the pricing sentence packs three distinct facts into one semicolon chain.

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, full schema coverage, and read-only annotations, the description already supplies the missing layers: cost, data freshness caveat, and fixed search parameters. The only unaddressed edge is what a call that returns zero flights does (and whether it is billed), which is a minor gap for a metered tool.

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 100%, so all five parameters are already documented, which sets the baseline at 3. The description only reinforces the origin/destination IATA convention ('e.g. JFK to LHR') and says nothing extra about limit or nonstopOnly semantics beyond what the schema states.

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?

States a specific verb and resource — 'One-way flight options with prices from Google Flights for a route and date' — and enumerates the exact payload (lowest fare, airlines, stops, times, duration). It also explicitly contrasts itself with the two named siblings, so an agent can distinguish it from hotels/travel tools without opening any schema.

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 gives the driving condition (a route and a date) and explicitly brackets the two named siblings as 'for a different need', with the condition that selects each. What is missing is any negative guidance, e.g. that this is a schedule/'from' price lookup rather than live tracking, but the positive routing is clear.

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