Free, no-login MCP server for searching and comparing flights with real-time pricing from multiple airlines and booking platforms worldwide.
Scored across 1 tool
With only one tool, there is no possibility of confusion. The tool's purpose is clearly distinct by default.
With a single tool, naming consistency is trivially perfect. The tool name 'search' is a simple verb, but no inconsistency exists.
The server has only one tool for flight search. While it covers the core purpose, the surface is thin; typically a flight server might include multiple operations like booking or status, but the tool explicitly limits scope to search.
The server provides a comprehensive search tool with detailed parameters, but lacks any action beyond searching (e.g., booking, modifying). The stated scope is search-only, so it is complete within that narrow definition, but leaves obvious gaps for a full flight service.
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.
| Name | Required | Description | Default |
|---|---|---|---|
| adults | No | Number of adult passengers (1-9). Defaults to 1. | |
| locale | No | Preferred language code (e.g. en, de, fr). Defaults to en. | en |
| origin | Yes | Departure city, airport name, or IATA code (e.g. 'Frankfurt', 'JFK', 'London Heathrow'). | |
| infants | No | Number of infants under 2 (0-9). Defaults to 0. | |
| children | No | Number of children aged 2-11 (0-9). Defaults to 0. | |
| currency | No | Preferred ISO 4217 currency code for prices (e.g. EUR, USD, GBP). Defaults to EUR. | EUR |
| trip_class | No | Cabin class: Y for economy, C for business. Defaults to Y. | Y |
| destination | Yes | Arrival city, airport name, or IATA code. | |
| return_date | No | Return date for round-trip. Omit for one-way flights. | |
| departure_date | Yes | Departure date. Accepts common formats such as YYYY-MM-DD, DD.MM.YYYY, or natural-language dates. |
| Name | Required | Description |
|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond annotations (readOnlyHint, idempotentHint, destructiveHint), the description adds real-time external API querying, price-ranked results grouped by stops, affiliate booking links, and 15-minute validity. It also clarifies it does not book flights, modify reservations, or store user data.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is well-structured, starting with core function, then usage guidelines, then behavioral details. It is informative but slightly long; however, each sentence serves a purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's complexity (10 parameters, real-time API, output with links and pricing), the description covers purpose, usage, behavioral traits, and limitations (15-minute validity). Output schema exists, so return values are covered. Complete for effective use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with each parameter described in the input schema. The description repeats that return_date can be omitted for one-way trips, which is already in the schema. No additional semantic depth beyond what the schema provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it searches live flight offers between origin and destination for given dates, supports one-way and round-trip with flexible passengers and cabin class. It distinguishes itself from non-flight searches, making the purpose unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says 'Use this when the user wants to compare available flights...' and 'Do not use it for rental cars, hotels, trains...', providing clear when-to-use and when-not-to-use guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
search
Add one secure layer between your agents and this server.