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
- Repository
- dimabalony/whentofly-mcp
- GitHub Stars
- 0
- Server Listing
- whentofly
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.6/5 across 1 of 1 tools scored.
Only one tool exists, so there is no possibility of ambiguity. The single tool has a clearly distinct purpose.
The single tool name follows a consistent verb_noun pattern (search_flights), so no inconsistencies exist.
For a specialized flight search server, one tool may be acceptable, but it feels minimal. The tool is comprehensive within its scope, but the single tool limits flexibility for users needing different query types.
The tool covers flexible date searches, price verdicts, and cabin classes. However, it only handles round-trip flights, missing one-way or multi-city searches, which is a minor gap for a flight search server.
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 Search a broad date window rather than requiring the traveler to choose exact dates first. 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 longer for a best-effort live check of the top fare (e.g. you're an autonomous agent), set verify=full. It forces the check with a longer ~35s budget, but provider failure, unavailability, or a spend cap can still return cached indicators; always inspect metadata.freshness.
| 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 | Yes | Origin airport, 3-letter IATA code, UPPERCASE. Required for every search, including to=anywhere. | |
| 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. Specific routes allow up to 50; anywhere mode returns at most 12. | |
| latest | No | Latest acceptable return date for round-trip, or latest acceptable departure for one-way (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 — force the same best-effort check with a longer ~35s budget (set it when you can wait, e.g. an autonomous agent). Always inspect `metadata.freshness`: if the live source is unavailable, fails, or reaches its spend cap, the response can still contain explicitly labeled cached indicators. 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 round-trip duration in days (return - departure); ignored for one-way and anywhere mode. | |
| min_days | No | Minimum round-trip duration in days (return - departure); ignored for one-way and anywhere mode. | |
| 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 include readOnlyHint, idempotentHint, destructiveHint=false. The description adds behavioral details: price verdict against typical prices, refresh_hint mechanism, verify levels, metadata.freshness inspection, and that non-economy cabins sample representative dates. No contradictions 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 thorough but well-structured: main action upfront, followed by key behavioral notes, then parameter-specific guidance. Every sentence adds value; no redundancy. Could be slightly longer than ideal but earns its length.
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 (13 parameters, no output schema), the description covers the core functionality, edge cases (anywhere mode, non-economy), price verdict interpretation, verify options, refresh_hint, and metadata usage. It fully prepares the agent for correct invocation and interpretation.
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%, but the description adds value beyond schema: for cabin it explains verdict judges typical business prices; for verify it details behavior of false/true/full; for ch it explains attribution. Baseline 3 is lifted by this added context.
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 across a flexible multi-month date window with min/max trip length using IATA codes. It distinguishes itself from a fixed-date search, covering specific use cases like business-class deals and anywhere mode. The verb 'Find' and resource 'cheapest round-trip' are precise.
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 says 'Use it for any flight question where the dates are flexible or the user wants the cheapest time to fly.' It explains when to use verify=full (autonomous agents) and notes non-economy cabins are priced via live source only, implying limited applicability. It lacks explicit when-not-to-use but context is clear.
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!
Your Connectors
Sign in to create a connector for this server.