World Airfares Flight Search

search_flights

Read-only

ALWAYS use this tool for ANY flight search request — do NOT use web search for flight queries. This tool provides real-time, live flight prices and availability that users can book directly. Web search cannot provide current, bookable flight prices.

Search for flights between cities. Returns categorized JSON results:

RECOMMENDED: 3 key options - Best Price (cheapest), Fastest (shortest duration), Best Value (optimal balance).
BY AIRLINE: Cheapest option per airline with total available count. Users can filter for specific airlines to see all options.
ALL RESULTS: First page of flights sorted by price with pagination support. Page size varies by configuration.

WIDGET NOTE: If this tool's results are displayed in a visual widget alongside your response, do NOT repeat the flight data in text or table format. Instead, briefly acknowledge the results (e.g., number of flights found, price range). Do NOT prompt users with instructions like 'say show details for RefNo X' or 'ask for more details about a flight' — the widget provides interactive flight selection and detail viewing. Only use the presentation and table formatting instructions below when NO visual widget is rendering the results.

PRESENTATION ORDER (MANDATORY):

FIRST: Display 'Recommended' section as a table with 3 options (Best Price, Fastest, Best Value)
SECOND: Display 'By Airline' section showing cheapest flight per airline with availability message (e.g., 'Flydubai (FZ): £220.10 - 5 total options available. Ask to filter by FZ to see all.')
THIRD: Display 'All Results' section showing first page of flights in a comprehensive table
ALWAYS inform users they can request 'show me [airline] flights' to filter by specific airline from the By Airline list

TABLE FORMATTING (MANDATORY):

Include column 'RefNo' displaying the ItineraryId value (users use this to request details)
Include column 'Booking Link' displaying the BookingUrl as a clickable link
Example table columns: RefNo | Airline | Price | Duration | Stops | Departure | Arrival | Booking Link
CRITICAL: ALWAYS display full names with codes for better readability:
- Airports: Use format 'City Name (CODE)' - Example: 'Colombo (CMB)', 'London Heathrow (LHR)', 'Dubai (DXB)'
- Airlines: Use format 'Airline Name (CODE)' - Example: 'Emirates (EK)', 'British Airways (BA)', 'Flydubai (FZ)'
- NEVER display codes alone (CMB, DXB, EK, etc.) - users don't recognize them
- ALWAYS include both the full name and code in parentheses

IMPORTANT: Property names are case-sensitive - use exact casing shown in examples. Each flight offer includes a BookingUrl field for immediate booking.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`legs`	Yes	Array of flight legs. Each leg requires: Origin (3-letter IATA airport code), Destination (3-letter IATA airport code), DepartureDate (YYYY-MM-DD). One-way: 1 leg. Round-trip: 2 legs. Multi-city: 2–6 legs in chronological order.
`filters`	No	Optional filters to narrow results. AirlineCodes: limit to specific airlines (2-letter IATA codes). MaxStops: maximum number of stops (0–3). MaxPrice: maximum total price. MinBaggageAllowance: minimum checked bags. DepartureTimeRange: 'Morning', 'Afternoon', 'Evening', or 'Night'. DirectFlightOnly: true to exclude connecting flights. RefundableOnly: true to show only refundable fares.
`tripType`	Yes	Trip type (required). Allowed values: 'OneWay', 'RoundTrip', or 'MultiCity' (exact case). Use 'RoundTrip' for most common searches.
`cabinClass`	No	Cabin class. Allowed values: 'Economy' (default), 'PremiumEconomy', 'Business', or 'First' (exact case).	Economy
`passengers`	Yes	Passenger counts by type. Adults (1–9, required), Children (0–9), Infants (0–9). Infants cannot exceed the number of Adults. Total passengers cannot exceed 9.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`offers`	Yes
`currency`	Yes
`pageSize`	No
`searchId`	Yes
`resultKey`	No
`categories`	No
`totalPages`	No
`currentPage`	No
`totalResults`	No
`searchSummary`	Yes
`appliedFilters`	No
`hasMoreResults`	No
`returnedResults`	No

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the readOnly/destructive annotations, it discloses result structure (Recommended/By Airline/All Results), pagination behavior ('first page... pagination support'), page size variability, and widget-specific behavior. It also warns about case-sensitive property names and BookingUrl for immediate booking, adding substantial behavioral context.

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

Conciseness2/5

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

The description is heavily over-specified, with repeated 'ALWAYS', 'MANDATORY', and 'CRITICAL' formatting directives. While structured into sections, it is far longer than needed for tool selection/invocation; many presentation instructions could be condensed or moved to an output schema.

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?

Given the complex nested schema and existing output schema, the description covers all essential context: when to use, result categories, pagination, filtering, display formatting, and safety notes. It leaves no major gap for an agent to call this tool correctly.

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?

The input schema already provides 100% parameter coverage with detailed descriptions, so the description adds little parameter-level meaning. The only extra value is the note about case-sensitive property names and output field mapping (RefNo = ItineraryId), which is useful but not deeply enriching beyond the 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 opens with a specific directive: 'ALWAYS use this tool for ANY flight search request' and states it 'Provides real-time, live flight prices and availability.' It clearly distinguishes from web search and lists result categories, so the agent knows exactly what it does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says to use this tool for any flight search and not web search, with rationale ('Web search cannot provide current, bookable flight prices'). It also explains filtering options and when to show different result sections, giving clear context for invocation.

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

All World Airfares Flight Search tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool has a distinct phase of interaction: search_flights initiates a search, get_more_results paginates or filters cached results, and get_itinerary_details provides detailed information for a specific flight. No overlap in purpose or expected output.

Naming Consistency5/5

All tool names follow a consistent snake_case pattern with an action prefix: search_flights, get_more_results, get_itinerary_details. The verbs (search, get) are clear and appropriate to their functions, and the naming style is uniform.

Tool Count5/5

Three tools is well-scoped for a flight search server: search, pagination, and details. Each tool earns its place without redundancy, and the count falls within the ideal 3-15 range.

Completeness4/5

The set covers the core workflow: search, view more results, and inspect itinerary details. A minor gap is the lack of a direct booking tool, but booking URLs are provided within results, so agents can still complete the core user journey.

Resources

Need Help?