Skip to main content
Glama

search_multi_city

Read-only

Find multi-city flight itineraries by defining two or more legs with origin, destination, and date. Returns first-leg options and a token to fetch next legs.

Instructions

Search a multi-city trip of two or more legs.

Each leg has origin and destination (IATA codes), date (YYYY-MM-DD) and optional times (hour ranges as in search_flights). The result lists the first leg; get_next_flights(departure_token) lists the next one.

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": {
      "legs": "<legs>"
    },
    "name": "search_multi_city"
  }
}

Input Schema

NameRequiredDescriptionDefault
legsYes
adultsNo
childrenNo
currencyNoEUR
max_stopsNo
cabin_classNoeconomy
max_resultsNo

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/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real behavioral detail beyond that: partial results (only the first leg is returned) and the pagination handoff via departure_token. It does not discuss availability, pricing caveats, or failure modes, so it is good but not exhaustive.

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?

Compact and front-loaded: purpose first, then leg structure, then the result/pagination behavior. The parenthetical cross-reference to search_flights for the times format is efficient, though it assumes familiarity with that sibling's schema.

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 need no explanation, and the description usefully notes the partial-result behavior and the follow-up call. Against seven parameters it leaves passenger counts, currency, max_stops, cabin_class, and max_results entirely undefined, which is a notable gap for a search tool where those options materially change results.

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 0%, so the description must carry the parameter burden, and it does so for the required 'legs' array: origin/destination are IATA codes, date is YYYY-MM-DD, and times are hour ranges as defined in search_flights — all meaning the bare schema titles do not convey. However, adults, children, currency, max_stops, cabin_class, and max_results are never mentioned, leaving the majority of the seven parameters documented only by their titles and defaults.

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 verb and resource and immediately states the defining constraint: 'Search a multi-city trip of two or more legs.' That 'two or more legs' clause is exactly what separates it from the sibling search_flights, so an agent can pick it without opening either schema.

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?

It gives concrete follow-up guidance: the result lists only the first leg, and get_next_flights(departure_token) lists the next one, which tells the agent how to drive the flow to completion. It never explicitly says when to choose this over search_flights for a single-leg query, so it stops short of full when/when-not coverage.

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