Skip to main content
Glama

Search empty legs

search_empty_legs
Read-onlyIdempotent

Finds current empty-leg flights by origin and/or destination (city, IATA/ICAO code, country, US state, region or area such as Greek Islands), dates, passengers, budget and aircraft class. Returns up to 20 offers with route, date, aircraft, seats, indicative price, a voidjet link and a pre-filled inquiry link; provider names are not included. When more offers match, refine summarises all matches (frequent destinations, date span, prices). With no match, charter_alternative may contain a regular charter via partner Villiers: NOT an empty leg; it names the partner and states that voidjet receives a fee from the partner.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_empty_legs"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoOrder of results: date (earliest departure first) or price (cheapest first).date
limitNoNumber of offers to return.
localeNoLanguage of texts and links in the result: en or de.en
offsetNoNumber of offers to skip, for paging.
originNoDeparture city or IATA/ICAO code (e.g. Nice, NCE), or a country, US state, region or area (e.g. Greece, Florida, Caribbean, Greek Islands).
date_toNoLatest departure date, at most 120 days after date_from.
date_fromNoEarliest departure date (YYYY-MM-DD), default today.
passengersNoNumber of passengers; only offers with at least this many seats.
destinationNoArrival city, IATA/ICAO code, country, US state, region or area.
max_price_eurNoMaximum price in EUR for the whole aircraft.
aircraft_classNoOnly these aircraft classes. Offers without a known aircraft type are excluded.

Output Schema

NameRequiredDescriptionDefault
limitYes
notesNo
totalYesNumber of matching offers in total.
noticeNoFee notice, the same in every search response. Pass it on to the user when you show offers.voidjet receives a fee from the provider or partner for some offers. This does not affect the order of results.
offsetYes
refineNoOnly when more offers match than returned: frequent destinations, date span and price range of all matches, to suggest how to narrow.
resultsYes
data_as_ofYes
resolved_toNo
resolved_fromNo
charter_alternativeNoOnly when no empty leg matches: a regular charter via a partner. NOT an empty leg; voidjet receives a fee from the partner.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Number of offers to return."
    • addedInput schema / properties / locale / description
      Added value: +"Language of texts and links in the result: en or de."
    • addedInput schema / properties / offset / description
      Added value: +"Number of offers to skip, for paging."
    • addedInput schema / properties / passengers / description
      Added value: +"Number of passengers; only offers with at least this many seats."
    • addedInput schema / properties / sort / description
      Added value: +"Order of results: date (earliest departure first) or price (cheapest first)."
  2. Changed6 schema fields changed
    • changedOutput schema / $defs / AgentFlight / properties / inquiry_possible / description
      Previous value: -"False for partner offers, which are requested on the partner site via the url."New value: +"False for offers listed by a partner, which are requested on the partner site via the url."
    • changedOutput schema / $defs / AgentFlight / properties / inquiry_url / description
      Previous value: -"Offer page with the inquiry form opened and pre-filled. The user enters name and email and sends it. Null for partner offers."New value: +"Offer page with the inquiry form opened and pre-filled. The user enters name and email and sends it. Null for offers listed by a partner."
    • changedOutput schema / $defs / CharterAlternative / properties / disclosure / default
      Previous value: -"Paid partner offer by Villiers; voidjet receives a commission if a booking results."New value: +"Charter via voidjet partner Villiers. voidjet receives a fee from the partner."
    • changedOutput schema / $defs / CharterAlternative / properties / notice / default
      Previous value: -"NOT AN EMPTY LEG. voidjet found no empty leg for this search. This is a regular private charter of the whole aircraft by voidjet partner Villiers, priced as a full charter and usually far above empty-leg prices. The ranges are indicative estimates from Villiers, not offers; confirmed prices are available on request on villiers.ai via url."New value: +"NOT AN EMPTY LEG. voidjet found no empty leg for this search. This is a regular private charter of the whole aircraft through voidjet's charter partner Villiers, priced as a full charter and usually far above empty-leg prices. The ranges are indicative estimates from Villiers, not offers; confirmed prices are available on request on villiers.ai via url."
    • changedOutput schema / properties / charter_alternative / description
      Previous value: -"Only when no empty leg matches: a regular charter via a partner. NOT an empty leg; a paid partner offer."New value: +"Only when no empty leg matches: a regular charter via a partner. NOT an empty leg; voidjet receives a fee from the partner."
    • addedOutput schema / properties / notice
      Added value: +{
      +  "default": "voidjet receives a fee from the provider or partner for some offers. This does not affect the order of results.",
      +  "description": "Fee notice, the same in every search response. Pass it on to the user when you show offers.",
      +  "title": "Notice",
      +  "type": "string"
      +}
  3. Changed2 schema fields changed
    • changedInput schema / properties / destination / description
      Previous value: -"Arrival city or IATA/ICAO code."New value: +"Arrival city, IATA/ICAO code, country, US state, region or area."
    • changedInput schema / properties / origin / description
      Previous value: -"Departure city or IATA/ICAO code, e.g. Nice or NCE."New value: +"Departure city or IATA/ICAO code (e.g. Nice, NCE), or a country, US state, region or area (e.g. Greece, Florida, Caribbean, Greek Islands)."
  4. Changed1 schema field changed
    • addedInput schema / properties / aircraft_class
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "enum": [
      +          "vlj",
      +          "light",
      +          "midsize",
      +          "super_midsize",
      +          "heavy",
      +          "ultra",
      +          "turboprop",
      +          "airliner_vip"
      +        ],
      +        "type": "string"
      +      },
      +      "maxItems": 8,
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Only these aircraft classes. Offers without a known aircraft type are excluded.",
      +  "title": "Aircraft Class"
      +}
  5. Changed3 schema fields changed
    • changedOutput schema / $defs / CharterAlternative / properties / disclosure / default
      Previous value: -"Partner offer by Villiers; voidjet receives a commission if a booking results."New value: +"Paid partner offer by Villiers; voidjet receives a commission if a booking results."
    • changedOutput schema / $defs / CharterAlternative / properties / notice / default
      Previous value: -"NOT AN EMPTY LEG. voidjet found no empty leg for this search. This is a regular private charter of the whole aircraft by voidjet partner Villiers, priced as a full charter and usually far above empty-leg prices. Say clearly to the user that this is not an empty leg before showing it. The ranges are indicative estimates from Villiers, not offers; for confirmed prices the user opens url and requests a quote on villiers.ai."New value: +"NOT AN EMPTY LEG. voidjet found no empty leg for this search. This is a regular private charter of the whole aircraft by voidjet partner Villiers, priced as a full charter and usually far above empty-leg prices. The ranges are indicative estimates from Villiers, not offers; confirmed prices are available on request on villiers.ai via url."
    • changedOutput schema / properties / charter_alternative / description
      Previous value: -"Only when no empty leg matches: a regular charter via a partner. NOT an empty leg; tell the user so."New value: +"Only when no empty leg matches: a regular charter via a partner. NOT an empty leg; a paid partner offer."
  6. Changed1 schema field changed
    • changedOutput schema / $defs / CharterAlternative / properties / disclosure / default
      Previous value: -"Partner offer by Villiers; voidjet receives a commission if a booking results. Keep this marking when showing the offer."New value: +"Partner offer by Villiers; voidjet receives a commission if a booking results."
  7. Changed3 schema fields changed
    • addedOutput schema / $defs / RefineOption
      Added value: +{
      +  "properties": {
      +    "city": {
      +      "title": "City",
      +      "type": "string"
      +    },
      +    "count": {
      +      "title": "Count",
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "city",
      +    "count"
      +  ],
      +  "title": "RefineOption",
      +  "type": "object"
      +}
    • addedOutput schema / $defs / Refinement
      Added value: +{
      +  "description": "Eingrenzungshilfe, wenn mehr passt als geliefert wird (10.10.2026, Robin):\nDer Assistent soll nicht pauschal \"grenzen Sie ein\" sagen, sondern konkret\nfragen koennen - \"Nizza (12), Genf (8) oder lieber ab Freitag?\".",
      +  "properties": {
      +    "destinations": {
      +      "default": [],
      +      "description": "Most frequent destinations among all matches.",
      +      "items": {
      +        "$ref": "#/$defs/RefineOption"
      +      },
      +      "title": "Destinations",
      +      "type": "array"
      +    },
      +    "earliest_date": {
      +      "anyOf": [
      +        {
      +          "format": "date",
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Earliest Date"
      +    },
      +    "latest_date": {
      +      "anyOf": [
      +        {
      +          "format": "date",
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Latest Date"
      +    },
      +    "origins": {
      +      "default": [],
      +      "description": "Most frequent origins among all matches (when no origin was given).",
      +      "items": {
      +        "$ref": "#/$defs/RefineOption"
      +      },
      +      "title": "Origins",
      +      "type": "array"
      +    },
      +    "price_max_eur": {
      +      "anyOf": [
      +        {
      +          "type": "integer"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Price Max Eur"
      +    },
      +    "price_min_eur": {
      +      "anyOf": [
      +        {
      +          "type": "integer"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "default": null,
      +      "title": "Price Min Eur"
      +    }
      +  },
      +  "title": "Refinement",
      +  "type": "object"
      +}
    • addedOutput schema / properties / refine
      Added value: +{
      +  "anyOf": [
      +    {
      +      "$ref": "#/$defs/Refinement"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Only when more offers match than returned: frequent destinations, date span and price range of all matches, to suggest how to narrow."
      +}
  8. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new context: provider names are withheld, result volume is capped at 20, and — most valuably — the commercial disclosure that a fallback charter names partner Villiers and that voidjet earns a fee from that partner. It does not discuss pagination or rates beyond what the schema says.

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?

A dense but well-ordered paragraph: what is searched, what comes back, then the two follow-up branches. Every clause carries information, though the multi-item parenthetical lists (geo types, result fields) make the opening sentence long and slightly harder to scan.

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 11 optional params, 100% schema coverage, full annotations, and an output schema, the description need not explain return values or argument syntax — and it doesn't overreach there. It closes the two important loops an agent would otherwise guess at (overflow → refine, empty → charter_alternative with disclosure). The only gap is the absence of guidance on when to choose this tool versus get_empty_leg or create_flight_alert.

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% with per-parameter descriptions, defaults, enums, and bounds, so the schema carries the parameter burden. The description only restates the supported dimensions (geo granularity, dates, passengers, budget, aircraft class) without adding syntax or edge-case semantics (e.g. how origin and destination combine, or why offset maxes at 40). 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?

Opens with a specific verb and resource ("Finds current empty-leg flights") and enumerates the matchable dimensions (origin/destination geo types, dates, passengers, budget, aircraft class). It also states the result shape (up to 20 offers with route, date, aircraft, seats, price, links), so an agent can distinguish this broad search from the singular get_empty_leg sibling without opening either schema.

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?

Gives clear downstream routing: when more offers exist, 'refine' summarises all matches; when nothing matches, 'charter_alternative' may hold a partner charter that is explicitly NOT an empty leg. There is no explicit exclusion telling an agent when to prefer get_empty_leg or create_flight_alert over this search, so it falls short of a full when/when-not statement.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources