Fly Travel Albania

Browse & filter offers (advisor, one call)

charter_offers

Read-onlyIdempotent

THE discovery tool: filters the whole cached charter inventory (hundreds of hotels) in ONE call by date, TOTAL budget, stars, board, zone, party and hotel features (aquapark, kids club, adults-only, beach, spa, luxury…). Built for "I have X EUR for 2 adults + a child, Antalya, 5 stars, aquapark, near the beach — what do you suggest?". Returns the price range, three quality tiers (economy-but-good / mid / premium) and a shortlist; advise from the tiers, never only the cheapest. Pass the date whenever the user has one (exact availability for that date) and the real party (exact-party cache is used when present). excluded_unknown_features tells how many hotels were dropped because their facilities are unknown. CACHED prices (from recent real searches on flytravel.al — not a live query; every row carries cached_at/age_minutes). Charter prices are PACKAGE TOTALS in EUR for the row's "party" (flight + hotel + transfers), NOT per person. party_match=false means the price is the 2-adult reference, not the total for the requested party — say so. A price belongs ONLY to its own "date": never present it as the price of another date.

Input Schema

TableJSON Schema

Name	Required	Description
`spa`	No	true = only hotels with spa / Turkish bath / sauna.
`date`	No	Departure date, format YYYY-MM-DD (recommended — exact availability for that date).
`zone`	No	Zone/resort filter substring, e.g. 'Belek', 'Alanya', 'Lara', 'Side', 'Kemer'.
`beach`	No	true = only hotels with a beach (own or nearby, per the hotel facts).
`board`	No	Board filter substring, e.g. 'all inclusive', 'ultra'.
`limit`	No	Shortlist size (default 12).
`adults`	No	Number of adults (default 2).
`luxury`	No	true = only hotels tagged luxury.
`nights`	No	Trip length in nights. Omit for the standard charter length (6 nights / 7 days). Most departures also sell 3-10 nights.
`aquapark`	No	true = only hotels with an aquapark / water park.
`kids_club`	No	true = only hotels with a kids / mini club.
`stars_min`	No	Minimum hotel star rating (1-5).
`adults_only`	No	true = only adults-only hotels; false = EXCLUDE adults-only hotels (use false for any party with children).
`destination`	No	Optional destination key ('antalya', 'bodrum'). Omit to search all.
`children_ages`	No	Age of each child AT DEPARTURE (0-14 = child; 15+ is counted as an adult automatically).
`private_beach`	No	true = only hotels listing a private / own beach.
`family_friendly`	No	true = only hotels with family facilities (kids club / kids pool / family rooms) and not adults-only.
`budget_total_max`	No	Max TOTAL budget in EUR for the whole party.
`budget_total_min`	No	Optional min total, to skip too-basic offers.

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedAug 31, 2026

addedInput schema / properties / adults

Added value: +{
+  "description": "Number of adults (default 2).",
+  "maximum": 6,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / adults_only

Added value: +{
+  "description": "true = only adults-only hotels; false = EXCLUDE adults-only hotels (use false for any party with children).",
+  "type": "boolean"
+}

addedInput schema / properties / aquapark

Added value: +{
+  "description": "true = only hotels with an aquapark / water park.",
+  "type": "boolean"
+}

addedInput schema / properties / beach

Added value: +{
+  "description": "true = only hotels with a beach (own or nearby, per the hotel facts).",
+  "type": "boolean"
+}

changedInput schema / properties / budget_total_max / description

Previous value: -"Max TOTAL budget in EUR for 2 adults."New value: +"Max TOTAL budget in EUR for the whole party."

addedInput schema / properties / children_ages

Added value: +{
+  "description": "Age of each child AT DEPARTURE (0-14 = child; 15+ is counted as an adult automatically).",
+  "items": {
+    "maximum": 17,
+    "minimum": 0,
+    "type": "integer"
+  },
+  "maxItems": 6,
+  "type": "array"
+}

addedInput schema / properties / family_friendly

Added value: +{
+  "description": "true = only hotels with family facilities (kids club / kids pool / family rooms) and not adults-only.",
+  "type": "boolean"
+}

addedInput schema / properties / kids_club

Added value: +{
+  "description": "true = only hotels with a kids / mini club.",
+  "type": "boolean"
+}

addedInput schema / properties / luxury

Added value: +{
+  "description": "true = only hotels tagged luxury.",
+  "type": "boolean"
+}

addedInput schema / properties / nights

Added value: +{
+  "description": "Trip length in nights. Omit for the standard charter length (6 nights / 7 days). Most departures also sell 3-10 nights.",
+  "maximum": 21,
+  "minimum": 2,
+  "type": "integer"
+}

addedInput schema / properties / private_beach

Added value: +{
+  "description": "true = only hotels listing a private / own beach.",
+  "type": "boolean"
+}

addedInput schema / properties / spa

Added value: +{
+  "description": "true = only hotels with spa / Turkish bath / sauna.",
+  "type": "boolean"
+}

changedInput schema / properties / zone / description

Previous value: -"Zone/resort filter substring, e.g. 'Belek', 'Alanya'."New value: +"Zone/resort filter substring, e.g. 'Belek', 'Alanya', 'Lara', 'Side', 'Kemer'."

First observedAug 26, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The description is rich with behavioral caveats beyond the read-only annotations: prices are cached, not live; prices are package totals in EUR, not per person; party_match=false means the price is a 2-adult reference; and a price belongs only to its own date. It also explains excluded_unknown_features. This is essential for the agent not to misrepresent results.

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

Conciseness5/5

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

The description is long but every sentence earns its place: it front-loads the core purpose, then adds a concrete example, then the output structure, then essential caveats about cache, pricing, and date-bounding. There is no filler or restating of schema.

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

Completeness5/5

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

With no output schema, the description takes on the burden of explaining what the tool returns: price range, three quality tiers, a shortlist, excluded_unknown_features, and party_match semantics. It covers the necessary context for an agent to call and interpret results correctly, even for a complex 19-parameter tool.

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 description coverage is 100%, so the input schema already documents all 19 parameters well. The description adds some context about party-exact cache usage and not presenting prices across dates, but these are largely behavioral rather than new parameter-level semantics. Baseline 3 is appropriate.

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?

The description states a specific verb+resource: it filters the whole cached charter inventory in one call by multiple criteria. It clearly differentiates itself from siblings by positioning itself as the discovery tool with an illustrative natural-language query, and by mentioning the one-call nature.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context on when to use the tool: for open-ended 'what do you suggest' queries, and instructs to pass the date and real party when available. It does not explicitly mention alternatives or exclusions, so it stops short of a 5.

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

All Fly Travel Albania 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?