Skip to main content
Glama
OctoTrip

OctoTrip Flights

Official

search

Read-onlyIdempotent

Search live flight offers between any two airports or cities worldwide. Compare prices, airlines, layovers, and booking links for one-way or round-trip travel with flexible passenger counts and cabin class.

Instructions

Searches live flight offers between an origin and destination for given travel dates. Supports one-way (omit return_date) and round-trip searches with flexible passenger counts and cabin class. Use this when the user wants to compare available flights, airlines, prices, layovers, or booking links for a specific route. Do not use it for rental cars, hotels, trains, or general travel planning unless the user has flight-search intent. The tool queries external flight aggregator APIs in real time, returns price-ranked results grouped by number of stops, and includes affiliate booking links. Results and booking links are valid for approximately 15 minutes due to real-time airline pricing. It does not book flights, modify reservations, charge users, or store user data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
adultsNoNumber of adult passengers (1-9). Defaults to 1.
localeNoPreferred language code (e.g. en, de, fr). Defaults to en.en
originYesDeparture city, airport name, or IATA code (e.g. 'Frankfurt', 'JFK', 'London Heathrow').
infantsNoNumber of infants under 2 (0-9). Defaults to 0.
childrenNoNumber of children aged 2-11 (0-9). Defaults to 0.
currencyNoPreferred ISO 4217 currency code for prices (e.g. EUR, USD, GBP). Defaults to EUR.EUR
trip_classNoCabin class: Y for economy, C for business. Defaults to Y.Y
destinationYesArrival city, airport name, or IATA code.
return_dateNoReturn date for round-trip. Omit for one-way flights.
departure_dateYesDeparture date. Accepts common formats such as YYYY-MM-DD, DD.MM.YYYY, or natural-language dates.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false. The description adds valuable behavioral context: queries external APIs in real time, results valid for ~15 minutes, returns price-ranked results grouped by stops, and includes affiliate links. No contradiction with annotations.

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?

The description is concise (about 100 words) and well-structured. It front-loads the core action, then provides usage guidelines, then behavioral details. Every sentence adds value without redundancy.

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 existence of an output schema, the description doesn't need to detail return values, but it still explains the return format (price-ranked, grouped by stops, affiliate links, validity period). It also covers what the tool does not do. Very complete for a search tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description adds context about parameter interaction (e.g., omitting return_date for one-way) and clarifies cabin class values. This adds modest value 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 clearly states the tool searches live flight offers between origin and destination for given dates. It specifies one-way and round-trip support, passenger counts, and cabin class. The verb 'searches' and resource 'live flight offers' are specific, and the tool is well-defined despite no siblings.

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?

The description explicitly tells when to use the tool (compare flights, prices, booking links) and when not to (rental cars, hotels, trains). It also clarifies that the tool does not book flights, modify reservations, or store data, providing clear boundaries.

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/OctoTrip/flights'

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