Free, no-login flight search with real-time pricing from multiple airlines.
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?
Annotations declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds significant behavioral context: real-time API queries, 15-minute validity of results/links, and explicit statements of what it does not do (book, modify, charge, store data). 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single paragraph of about 6 sentences, front-loaded with the core purpose. Each sentence is functional and adds value. It is concise but could benefit from slightly more structured presentation (e.g., separate sections for usage and behavior), but overall well-written.
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?
Considering the complexity (10 parameters, 3 required, output schema present), the description covers the use case, data source, result format, and limitations. It explains the real-time nature and includes what the tool does not do. An output schema exists, so return values are accounted for separately. The description is 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.
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 reinforces the trip-type parameter (omit return_date for one-way) but does not add new parameter-level details beyond what the schema already provides. It offers general context but not deeper semantics.
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 specifies the tool's action: 'Searches live flight offers between an origin and destination for given travel dates.' It distinguishes one-way and round-trip searches and explicitly states it is not for other travel services like rental cars or hotels. Even though there are no sibling tools, the description differentiates from non-flight searches effectively.
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?
The description explicitly tells when to use the tool ('when the user wants to compare available flights...') and when not to ('Do not use it for rental cars, hotels, trains...'). It provides context about real-time queries, price ranking, and affiliate links, offering clear usage 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. Dates show when Glama detected each change.
searchClaiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
Free, no-login rental car search with real-time pricing.
Live flight prices and working booking links for AI agents and travel apps.
Search award flight availability and points pricing across 27 airlines and 23 loyalty programs.
Flight search & booking for AI agents. 400+ airlines, $20-50 cheaper than OTAs.
Add one secure layer between your agents and this server.
With only one tool, there is no possibility of confusion between tools. The 'search' tool has a clear and distinct purpose.
The single tool is named 'search', which is a simple, appropriate verb. There are no other tools to compare for consistency, but the name aligns with its function.
A single tool for a 'Flights' server is too thin. While the search tool is functional, an agent would likely expect additional tools for booking, modifying, or checking flight status, making the count feel insufficient.
The search tool covers its described scope well (one-way/round-trip, flexible parameters, real-time results). However, the server lacks any other flight-related operations such as booking or managing reservations, which are obvious gaps for a flights server.
