Skip to main content
Glama

Fly Travel Albania

by al.flytravel

Build a booking search link

booking_link
Read-onlyIdempotent

Deep link into the live charter search results for a destination, date, party and optional trip length — hand this URL to the user to see live availability and book. Children are ages 0-14 at departure; ages 15+ count as adults. Pure URL builder (no data).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesDeparture date, format YYYY-MM-DD.
adultsNoNumber of adults (default 2).
nightsNoTrip length in nights. Omit for the standard charter length (6 nights / 7 days). Most departures also sell 3-10 nights.
destinationYesDestination key, e.g. 'antalya'.
children_agesNoAge of each child AT DEPARTURE (0-14 = child; 15+ is counted as an adult automatically).

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description adds that the tool is a 'Pure URL builder (no data)' and clarifies child age behavior at departure. This goes beyond the annotations by explicitly defining the output as a URL and the no-side-effect nature.

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?

The description is concise and front-loaded with the core purpose. All sentences are relevant, though the child-age sentence partly duplicates the schema's own parameter description, which keeps it from a perfect score.

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?

With no output schema, the description clearly states the return is a URL. Combined with full schema coverage and readOnly/idempotent annotations, the tool is sufficiently described for an agent to invoke it correctly.

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 schema already documents all five parameters. The description adds the 'children ages 0-14 at departure' rule and 'optional trip length' phrasing, but these largely mirror the schema's existing property descriptions, providing limited additional value.

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 clearly states the tool builds a deep link into live charter search results for a destination, date, party, and optional trip length, and that the output is a URL to hand to the user. It differentiates itself from data-returning sibling tools with 'Pure URL builder (no data)'.

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 for when to use the tool: when the user wants to see live availability and book by receiving a URL. It does not explicitly name alternatives or exclusions, but the intended use case is unambiguous.

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 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation4/5

Most tools have clearly distinct roles, and the charter_* family is carefully delineated (cheapest by destination, cheapest by date window, filtered discovery, single hotel, comparison). There is still some surface-level overlap between charter_cheapest, charter_flexible_dates, and charter_offers, though the descriptions do enough to prevent major misselection.

Naming Consistency4/5

The naming is generally consistent and readable: charter_* tools share a strong prefix, and hotel_details/compare_hotels/tours_list/tour_details follow predictable noun-based patterns. Minor deviations like booking_link (verb+noun) and prices_digest (noun+noun) do not create real confusion.

Tool Count5/5

Twelve tools is well within the ideal range for a travel-domain server, and each tool covers a distinct query pattern: discovery, cheapest pricing, flexible dates, specific hotels, comparisons, static details, tours, and booking links. The count feels justified rather than padded.

Completeness4/5

The surface covers the main user journey well: find charters, filter by budget/features, compare hotels, get hotel details, check tours, and obtain booking links. Minor gaps exist, such as no non-charter package filtering by date/budget and no standalone flight/transfer search, but agents can still complete realistic travel-planning tasks.

Resources