World Airfares Flight Search

get_more_results

Read-only

Get additional pages of flight search results from cache. Use this when the user asks for 'more results', 'next page', 'show me more flights', or wants to see flights beyond the initial results. Optionally apply filters to cached results (airline, max stops, max price) without making a new API call. Retrieves results instantly from cache. Requires the searchId from a previous search response.

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 summarize the page results. Do NOT prompt users with instructions like 'say show details for RefNo X' — the widget provides interactive flight selection and detail viewing. Only use the table formatting instructions below when NO visual widget is rendering the results.

TABLE FORMATTING (MANDATORY):

ALWAYS format results as a comparison table
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
Include pagination info and offer details below table
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

Each flight offer includes a BookingUrl field for immediate booking.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page number to retrieve (1-based integer). Page 1 was already returned by the initial search. Use 2 for next page, 3 for third page, etc. Default: 2
`filters`	No	Optional filters to apply to the cached results without making a new API call. AirlineCodes: limit to specific airlines (2-letter IATA codes). MaxStops: maximum number of stops (0–3). MaxPrice: maximum total price. DepartureTimeRange: 'Morning', 'Afternoon', 'Evening', or 'Night'. DirectFlightOnly: true to exclude connecting flights.
`searchId`	Yes	The searchId from the previous search response (found in the 'searchId' field of the JSON response).

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.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is known. The description adds that results are retrieved instantly from cache and that filters are applied without a new API call, which are useful behavioral facts. It also provides extensive output formatting instructions (widget note, table format), which go beyond the schema and help the agent present results correctly.

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 description is well-structured with a leading purpose sentence, followed by usage guidance, a widget note, and mandatory formatting instructions. It is long due to the detailed table formatting requirements, but these instructions are necessary for correct agent behavior. It is not wasteful, though it could be slightly more concise.

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?

The description provides all necessary context: when to use, how to use, what parameters mean (already in schema), and how to format output. It even includes detailed formatting rules for airports and airlines. Since an output schema exists, return values need not be described. The tool is fully specified, making it complete for an agent to invoke 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 schema already provides detailed descriptions for all three parameters, so the description adds little extra meaning. It does summarize the filter options at a high level and reiterates the requirement for searchId, but these are already present in the schema. Thus the baseline of 3 applies.

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 clear verb-resource statement: 'Get additional pages of flight search results from cache.' It distinguishes from siblings by specifying it operates on cached results, whereas search_flights likely handles initial searches and get_itinerary_details handles specific itineraries. It also lists concrete user intents like 'more results' and 'next page', making the tool's scope unambiguous.

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?

The description explicitly tells when to use this tool: when the user asks for more results, next page, or wants to filter existing results. It also notes that this avoids a new API call, which helps the agent decide between this and search_flights. However, it does not explicitly name alternative tools or state when not to use it, so it falls just short of a 5.

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?