Skip to main content
Glama

get_next_flights

Read-only

Lists return flights or the next multi-city leg for a flight offer using its departure token, so you can continue planning round-trip or multi-city itineraries.

Instructions

List return flights, or the next multi-city leg, for an offer's departure_token.

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": {
      "departure_token": "<departure_token>"
    },
    "name": "get_next_flights"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_resultsNo
departure_tokenYes

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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and external-data profile is covered. The description contributes that this is a continuation step retrieving subsequent itinerary legs, but says nothing about token validity/expiry, result caps, or pagination behavior.

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?

A single front-loaded sentence with no filler, stating the resource before the keying parameter. It is efficient, though the terseness leaves no room for the usage or parameter detail the schema omits.

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 only two parameters, a documented output schema, and annotations covering the read-only/open-world profile, the description is close to sufficient for correct invocation. The remaining gap is the undocumented max_results parameter and the absence of any hint about obtaining a valid token.

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 must carry parameter meaning. It adds real context for departure_token by tying it to 'an offer', but leaves max_results completely unexplained (including its default of 15) and does not say where a token comes from.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb ('List') and resource ('return flights, or the next multi-city leg'), keyed to a departure_token. The 'next multi-city leg' phrasing implicitly separates it from the initial search tools, but it never names search_flights or search_multi_city to make the boundary explicit.

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?

Saying it works 'for an offer's departure_token' implies this is a follow-up call made after an offer has been selected, which is a useful usage signal. However, there is no explicit when-to-use clause, no statement of what to do if no token exists, and no routing to a sibling for initial flight search.

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