weekendflights

Cheapest cached weekends from one origin

cheapest_weekends

The cheapest weekends from one origin across every destination that has a calendar under these filters, sorted by price. Optional month filter (yyyy-mm). Takes the same filters as weekend_prices. This tool reads what is already priced; it does not search every destination. A destination that is absent can be priced with one weekend_prices call for that pair. Pro only: this tool is Anywhere (every destination from one origin). Without Pro it answers pro_required with the Anywhere page url. One route at a time is free with weekend_prices.

Input Schema

Name	Required	Description
`cabin`	No	Default "economy".
`combo`	No	Trip shape. Default "fri-sun".
`limit`	No	How many weekends to return. Default 10.
`month`	No	Limit to one month, format yyyy-mm.
`stops`	No	"any" (default) or "nonstop".
`adults`	No	Default 1.
`origin`	Yes	Departure airport IATA code, e.g. "ZRH".
`out_to`	No	Latest outbound departure, "HH:MM".
`ret_to`	No	Latest return departure, "HH:MM".
`infants`	No	Default 0.
`children`	No	Default 0.
`currency`	No	ISO 4217 code. Default: the native currency of the origin.
`out_from`	No	Earliest outbound departure, "HH:MM".
`ret_from`	No	Earliest return departure, "HH:MM".

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 13, 2026

changedInput schema / properties / combo / description

Previous value: -"Weekend shape. Default \"fri-sun\"."New value: +"Trip shape. Default \"fri-sun\"."

changedInput schema / properties / combo / enum

Previous value: -[
-  "thu-sun",
-  "thu-mon",
-  "thu-sat",
-  "fri-sun",
-  "fri-mon",
-  "fri-sat",
-  "sat-mon",
-  "sat-sun",
-  "sat-sat"
-]New value: +[
+  "mon-mon",
+  "mon-tue",
+  "mon-wed",
+  "mon-thu",
+  "mon-fri",
+  "mon-sat",
+  "mon-sun",
+  "tue-tue",
+  "tue-wed",
+  "tue-thu",
+  "tue-fri",
+  "tue-sat",
+  "tue-sun",
+  "tue-mon",
+  "wed-wed",
+  "wed-thu",
+  "wed-fri",
+  "wed-sat",
+  "wed-sun",
+  "wed-mon",
+  "wed-tue",
+  "thu-thu",
+  "thu-fri",
+  "thu-sat",
+  "thu-sun",
+  "thu-mon",
+  "thu-tue",
+  "thu-wed",
+  "fri-fri",
+  "fri-sat",
+  "fri-sun",
+  "fri-mon",
+  "fri-tue",
+  "fri-wed",
+  "fri-thu",
+  "sat-sat",
+  "sat-sun",
+  "sat-mon",
+  "sat-tue",
+  "sat-wed",
+  "sat-thu",
+  "sat-fri",
+  "sun-sun",
+  "sun-mon",
+  "sun-tue",
+  "sun-wed",
+  "sun-thu",
+  "sun-fri",
+  "sun-sat"
+]

First observedOct 3, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that it reads already-priced cached data rather than live-searching every destination, that it requires Pro, and that non-Pro callers get a pro_required response with the Anywhere page URL. It stops short of stating cache freshness/staleness or any rate limits, which are the remaining behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose and sorted-by-price behavior, then caveats and gating. Each sentence is informative, though weekend_prices is referenced twice and the filter-inheritance line slightly overlaps with the fallback line.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers behavior, prerequisites, failure mode, and the alternative tool, which is strong for a tool with no annotations and no output schema. The one omission is a hint about the shape of the returned weekend list, which the description only gestures at with 'sorted by price'.

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

Parameters3/5

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

Schema coverage is 100%, so all 14 parameters are already documented in the schema, including the month format and defaults. The description adds only that it takes the same filters as weekend_prices, which is routing context rather than new parameter meaning, so the baseline 3 applies.

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?

States a specific verb and resource with scope: the cheapest weekends from one origin across every destination with a calendar, sorted by price. It explicitly contrasts with weekend_prices (one route) and the Pro-only 'Anywhere' behavior, so an agent can distinguish it from siblings without opening a schema.

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?

Gives explicit when-to-use and when-not: use this for a whole-origin scan, but if a destination is absent it can be priced with a single weekend_prices call; one route at a time is free with weekend_prices. It also names the Pro-only precondition and the fallback response.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All weekendflights tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?