Skip to main content
Glama

search_flights

Read-only

Find one-way or round-trip flights by origin, destination, and date, then filter by stops, cabin, times, price, airlines, and bags to compare options.

Instructions

Search one-way or round-trip flights on Google Flights.

origin and destination are IATA codes; separate several with commas, e.g. "BRU,CRL". With return_date the result lists outbound flights and get_next_flights(departure_token) lists the return flights. outbound_times and return_times are hour ranges, "6,12" for departure or "6,12,10,18" for departure and arrival. max_stops 0 is nonstop only; bags counts carry-on bags. Airline filters take 2-letter IATA codes or STAR_ALLIANCE, SKYTEAM, ONEWORLD. deep_search is slower but closer to the browser.

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": {
      "origin": "<origin>",
      "destination": "<destination>",
      "departure_date": "<departure_date>"
    },
    "name": "search_flights"
  }
}

Input Schema

NameRequiredDescriptionDefault
bagsNo
adultsNo
originYes
sort_byNotop
childrenNo
currencyNoEUR
max_priceNo
max_stopsNo
cabin_classNoeconomy
deep_searchNo
destinationYes
max_resultsNo
return_dateNo
return_timesNo
departure_dateYes
outbound_timesNo
exclude_airlinesNo
include_airlinesNo

Output Schema

NameRequiredDescriptionDefault
countYes
offersYes
total_foundYes
price_insightsYes
google_flights_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds genuinely non-obvious behavior in noting deep_search is slower but closer to the browser, and that the result list is outbound-only when return_date is set. It doesn't discuss rate limiting, potential scraping failures, or max_results interaction with deep_search.

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?

Opens with the core capability, then spends the remainder on parameter syntax an agent cannot infer. Each sentence adds information; nothing is restated from the schema or annotations.

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 values needn't be described, and the trickiest parameters (times, stops, alliances) are explained. But with 18 parameters and zero schema coverage, leaving max_price, sort_by, max_results, cabin_class, currency and passenger counts undocumented is a meaningful gap for a tool of this complexity.

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 0%, so the description carries the full burden, and it delivers real syntax for origin/destination comma lists, outbound_times/return_times hour-range formats, max_stops 0, bags, and airline alliance codes. However, roughly half the parameters (adults, children, currency, max_price, cabin_class, sort_by, max_results, departure_date) get no mention, so compensation is partial.

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 — 'Search one-way or round-trip flights on Google Flights' — and the round-trip branch is defined by the presence of return_date. The agent can tell this apart from get_next_flights and search_multi_city immediately.

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?

Explicitly hands off to get_next_flights(departure_token) for return legs, which is a real routing decision an agent would otherwise miss, and clarifies one-way vs round-trip via return_date. It does not say when to prefer search_multi_city or get_booking_options, so the alternative coverage is incomplete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.