voidjet empty legs

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, and a paid partner offer.

Input Schema

Name	Required	Description	Default
`sort`	No		date
`limit`	No
`locale`	No		en
`offset`	No
`origin`	No	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).
`date_to`	No	Latest departure date, at most 120 days after date_from.
`date_from`	No	Earliest departure date (YYYY-MM-DD), default today.
`passengers`	No
`destination`	No	Arrival city, IATA/ICAO code, country, US state, region or area.
`max_price_eur`	No	Maximum price in EUR for the whole aircraft.
`aircraft_class`	No	Only these aircraft classes. Offers without a known aircraft type are excluded.

Output Schema

Name	Required	Description
`limit`	Yes
`notes`	No
`total`	Yes	Number of matching offers in total.
`offset`	Yes
`refine`	No	Only when more offers match than returned: frequent destinations, date span and price range of all matches, to suggest how to narrow.
`results`	Yes
`data_as_of`	Yes
`resolved_to`	No
`resolved_from`	No
`charter_alternative`	No	Only when no empty leg matches: a regular charter via a partner. NOT an empty leg; a paid partner offer.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 20, 2026

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)."

Changed1 schema field changedOct 20, 2026

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"
+}

Changed3 schema fields changedOct 11, 2026

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."

Changed1 schema field changedOct 11, 2026

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."

Changed3 schema fields changedOct 10, 2026

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."
+}

First observedOct 9, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuinely useful disclosure beyond that – provider names are withheld, up to 20 offers cap, and the no-match fallback is explicitly flagged as NOT an empty leg and a paid partner offer via Villiers. That last point is important behavioural context for the caller.

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 purpose, then the return shape, then the two outcome branches – a sensible order with no filler sentences. It is dense (one long paragraph with semicolon-chained clauses) but every clause carries information about results or fallbacks rather than restating the name.

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?

For an 11-parameter, optional-only search tool with an output schema, the definition covers purpose, return composition, result cap and the no-match path, which is what an agent most needs. It does not explain how limit/offset interact with the stated 20-offer cap or what locale changes, leaving a small gap in paging behaviour.

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

Parameters4/5

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

With 55% schema coverage and 11 parameters, the description compensates by naming the searchable dimensions (origin/destination geography forms, dates, passengers, budget/cap price, aircraft class) and clarifying that aircraft_class filtering excludes offers with unknown type. It adds little on sort, limit, offset and locale, which govern paging and result ordering.

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 (finds/searches) and resource (current empty-leg flights) plus the full set of search dimensions (origin/destination including city, IATA/ICAO, country, state, region, area, dates, passengers, budget, aircraft class). It routes the agent clearly versus sibling get_empty_leg by describing list/refine semantics and names the no-match fallback (charter_alternative) so the agent knows this is not a charter-quote tool.

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 usage context: use it to search current empty legs with flexible geography, and explains the two outcome branches – refine summarises when more matches exist, charter_alternative appears when nothing matches. It never explicitly says when NOT to use it versus get_empty_leg or request_charter_quote, so selection between siblings is still partly inferred.

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

All voidjet empty legs 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?