whentofly
Server Details
whentofly: flight search for AI agents — cheapest flexible-date round-trips + buy/wait verdict
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.3/5 across 1 of 1 tools scored.
With only one tool, there is no ambiguity. The tool's purpose is clearly defined and distinct.
The single tool name 'search_flights' follows a clear verb_noun pattern, which is consistent with best practices.
A single tool for a flight search server feels under-scoped. While the tool is powerful, it only handles flexible round-trip searches, missing fixed-date or one-way options that users might expect.
The tool covers flexible date round-trip searches with price verdicts and cabin support, but lacks support for one-way, multi-city, or specific date searches, leaving notable gaps for a flight search domain.
Available Tools
1 toolsearch_flightsARead-onlyIdempotentInspect
Find the cheapest round-trip across a FLEXIBLE multi-month date window with a min/max trip length — e.g. "10–15 days, anytime Sep–Nov". This is the flexible-date search the big flight tools (Google Flights, Kayak, Skyscanner, Kiwi) keep behind their consumer UI and don't expose via API. Pass origin/destination as IATA codes, an earliest/latest date window, and min/max trip duration; get back a ranked list of the cheapest fares (with booking links) plus a price verdict — an honest read of whether the cheapest fare is low, typical, or high versus the route's usual price, or unknown when we lack a usable typical-price band (a price-level read, not a buy-now-or-wait timing prediction). Supports cabin class: pass cabin=business (or premium_economy/first) to find business-class deals — the verdict then judges the fare against that cabin's OWN typical prices, and metadata.deal_signal flags a business fare below its typical band. Use it for any flight question where the dates are flexible or the user wants the cheapest time to fly. If metadata.refresh_hint is present, you may repeat the same call after the suggested delay to get live-verified prices. If you can wait ~30s for the freshest fully-verified prices (e.g. you're an autonomous agent), set verify=full — the top result is then live-verified with no cached_indicators fallback.
| Name | Required | Description | Default |
|---|---|---|---|
| ch | No | Acquisition channel tag (e.g. web, mcp, a campaign name). Encoded with the route into the affiliate link's sub_id so a future commission can be attributed to this channel in the Travelpayouts dashboard. Defaults to 'direct'. Sanitized to [a-z0-9-]; capped at 64 chars. | direct |
| to | No | Destination airport, 3-letter IATA code, UPPERCASE. Pass `anywhere` (or omit) to get the cheapest destinations from the origin instead of a specific route. | |
| from | No | Origin airport, 3-letter IATA code, UPPERCASE. Required for a specific route; with to=anywhere it may be omitted to auto-detect from the caller's IP country. | |
| cabin | No | Cabin class: economy (default), premium_economy, business, or first. Use cabin=business to find business-class deals — the price verdict then judges the fare against the route's typical BUSINESS prices, and metadata.deal_signal flags a business fare below its own typical band. Non-economy cabins are priced via the live Google Flights source only (the cached calendar source covers economy), so results sample representative dates in the window. | economy |
| top_n | No | Maximum number of results to return, sorted cheapest-first. | |
| latest | No | Latest acceptable return date (ISO YYYY-MM-DD). Window from earliest must be ≤365 days. Required for a specific route; ignored in anywhere mode. | |
| verify | No | How hard to live-verify the top result against Google Flights (SerpApi). `false` (default): the check still runs automatically on a fresh search when the top isn't already a live price, within a client-aware time budget. `true`: force the check even on a cache hit. `full`: THOROUGH mode — wait for complete live verification and return the freshest prices with NO cached_indicators fallback (a longer ~35s budget; set it when you can wait, e.g. an autonomous agent). No-op unless a SerpApi key is configured. | false |
| one_way | No | If true, search one-way flights; return_date and duration_days will be null. | |
| currency | No | Result currency, 3-letter ISO code UPPERCASE. | USD |
| earliest | No | Earliest acceptable departure date (ISO YYYY-MM-DD). Required for a specific route; ignored in anywhere mode. | |
| max_days | No | Maximum trip duration in days (return - departure). | |
| min_days | No | Minimum trip duration in days (return - departure). | |
| max_transfers | No | Maximum number of transfers/layovers per leg. 0 = nonstop only, 1 = up to 1 stop, etc. Omit for no filter. |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint=true and idempotentHint=true, so the description primarily adds value by detailing the price verdict (a price-level read, not a timing prediction), cabin class behavior (judging fare against its own typical band), and verify modes. It does not contradict annotations and adds useful context, earning a score above the baseline.
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 thorough but slightly verbose. It is well-structured with front-loaded purpose, clear sentences, and no wasted words. Every sentence adds value, but could be trimmed slightly without loss. Still, it is appropriately sized for the tool's complexity.
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 has 13 parameters, no output schema, and no siblings, the description covers purpose, parameters, output type (ranked list, price verdict), and usage scenarios. It does not explicitly list output fields, but the descriptions of parameters and behavior provide good context. It is nearly complete for an agent to use 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 coverage is 100% for all 13 parameters, so baseline is 3. The description adds meaning by explaining how parameters work together in the flexible search context, e.g., the purpose of min_days/max_days, how cabin affects source, and the anywhere mode. This extra context justifies a 4.
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 the tool finds the cheapest round-trip with flexible multi-month date windows and min/max trip length, using the example '10–15 days, anytime Sep–Nov'. It explicitly contrasts with typical flight APIs by noting this is the flexible search that big tools don't expose, making the purpose very specific and distinct.
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 states when to use: 'for any flight question where the dates are flexible or the user wants the cheapest time to fly'. It also provides context on using verify=full for autonomous agents and handling refresh_hint. While it lacks explicit exclusions or alternatives, the guidance is clear and practical.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
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
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.
Discussions
No comments yet. Be the first to start the discussion!