Villiers Charter

search_empty_legs

Read-onlyIdempotent

Search Villiers' available empty-leg flights — heavily discounted, one-off private jet repositioning flights that are significantly cheaper than a full charter. Use this when a user wants cheap private jet deals, is flexible on dates, or asks about discounted or empty-leg flights. Optionally filter by origin, destination or region. Each result links to the specific flight to view and enquire.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max results (default 20, max 50)
`offset`	No	Pagination offset (default 0). Call again with offset=next_offset from the previous response to page past the first `limit` results — see has_more/next_offset in the output.
`origin`	No	Origin city / airport name / IATA / ICAO, e.g. London or LHR or EGLL. Optional — mirrors destination, filters strictly on the departure side. Useful for a 'departing near me' search.
`region`	No	Region filter: europe / americas / asia / all. Optional.
`destination`	No	Destination city / airport name / IATA / ICAO, e.g. Nice or NCE. Optional.

Output Schema

TableJSON Schema

Name	Required	Description
`count`	No	Number of empty legs returned
`offset`	No	The offset this response was generated at
`summary`	No
`has_more`	No	True if more results exist beyond this page
`next_step`	No
`empty_legs`	No
`next_offset`	No	Offset to pass in the next call to continue paging; null when has_more is false
`total_available`	No	Total matching empty legs available

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 10, 2026

addedInput schema / properties / offset

Added value: +{
+  "description": "Pagination offset (default 0). Call again with offset=next_offset from the previous response to page past the first `limit` results — see has_more/next_offset in the output.",
+  "type": "integer"
+}

addedOutput schema / properties / has_more

Added value: +{
+  "description": "True if more results exist beyond this page",
+  "type": "boolean"
+}

addedOutput schema / properties / next_offset

Added value: +{
+  "description": "Offset to pass in the next call to continue paging; null when has_more is false",
+  "type": "integer"
+}

addedOutput schema / properties / offset

Added value: +{
+  "description": "The offset this response was generated at",
+  "type": "integer"
+}

Changed1 schema field changedAug 26, 2026

addedInput schema / properties / origin

Added value: +{
+  "description": "Origin city / airport name / IATA / ICAO, e.g. London or LHR or EGLL. Optional — mirrors destination, filters strictly on the departure side. Useful for a 'departing near me' search.",
+  "type": "string"
+}

First observedMay 31, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds that results link onward to view/enquire, which is useful, but it does not disclose behavioral caveats such as availability uncertainty or whether results are real-time. No annotation contradiction exists.

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?

Three focused sentences: an upfront definition of the resource, clear usage conditions, and a brief filter summary. No filler or redundant restatement of the tool name or 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 required parameters, a complete input schema, a rich output schema, and strong annotations, the description is fully sufficient for an agent to decide when to call the tool and what to expect. The description also usefully notes that each result links to an enquiry flow.

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 all five parameters fully documented including defaults, formats, and pagination behavior. The description only summarizes that origin, destination, or region filters are optional, adding little beyond what the schema already provides.

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 opens with a specific verb and resource ('Search Villiers' available empty-leg flights') and clearly positions the tool as the discovery layer for discounted repositioning flights. It is unambiguously distinct from the sibling tools, which handle confirmation status, estimates, and confirmation requests.

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 explicit 'Use this when...' triggers: cheap private jet deals, flexible dates, or empty-leg/discounted flight requests. It does not explicitly name sibling alternatives or state when not to use the tool, but the use cases and sibling names make the intended context clear.

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

All Villiers Charter 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?