Skip to main content
Glama
saikandikatta

cheapflights-mcp

Search Dates

search_dates
Read-onlyIdempotent

Find the cheapest travel dates between two airports within a date range. Supports one-way and round-trip searches for flexible trip planning.

Instructions

Find the cheapest travel dates between two airports within a date range.

Returns a list of dates with their prices, useful for flexible travel planning. Supports both one-way and round-trip searches.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
originYesDeparture airport IATA code(s), comma-separated for multiple (e.g., 'JFK' or 'JFK,LGA')
destinationYesArrival airport IATA code(s), comma-separated for multiple (e.g., 'LHR' or 'LHR,CDG')
start_dateYesStart of date range in YYYY-MM-DD format
end_dateYesEnd of date range in YYYY-MM-DD format
trip_durationNoTrip duration in days for round-trips
is_round_tripNoSearch for round-trip flights
airlinesNoFilter by airline IATA codes (e.g., ['BA', 'AA'])
cabin_classNoCabin class: ECONOMY, PREMIUM_ECONOMY, BUSINESS, FIRSTECONOMY
max_stopsNoMaximum stops: ANY, NON_STOP, ONE_STOP, TWO_PLUS_STOPSANY
departure_windowNoDeparture time window in 'HH-HH' 24h format (e.g., '6-20')
sort_by_priceNoSort results by price (lowest first)
passengersNoNumber of adult passengers

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds that it returns a list of dates with prices, which is consistent, but does not disclose additional behavioral traits like rate limits or data freshness.

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?

Three sentences, front-loaded with main purpose, no extraneous words. Highly efficient.

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?

Given rich schema (100% coverage), annotations, and output schema, the description adequately covers core functionality and return values. Could mention more about filtering options or result format nuances.

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 baseline is 3. The description only adds context about one-way/round-trip searches, which is already covered by the is_round_trip parameter schema.

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 clearly states the verb 'find' and resource 'cheapest travel dates between two airports within a date range', differentiating from sibling tools find_airports and search_flights.

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?

The description implies usage for flexible travel planning and notes support for one-way/round-trip, but does not explicitly guide when to use this tool versus search_flights or provide exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/saikandikatta/cheapflights-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server