SkyAccess

Search empty leg flights

search_empty_legs

Read-onlyIdempotent

Search available empty leg flights by origin, destination, date range, passenger count, and an optional max_price ceiling. Returns up to 5 matching flights with route, departure time, whole-aircraft price (taxes and fees shown at checkout), aircraft type, available seats, and a booking link. Empty legs are discounted private jet availability on specific routes. A flight with price: null has no published price (shown on SkyAccess as "Contact for price"). Such flights are included even when max_price is set, because their price is unknown; they are not confirmed to be within the cap.

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

Name	Required	Description
`origin`	No	Departure city or airport code (e.g. "Los Angeles" or "LAX")
`max_price`	No	Optional price ceiling in USD (whole-aircraft price; taxes and fees shown at checkout). Legs priced above this figure are excluded. Legs with no published price (price: null, shown as "Contact for price") are still included because their price is unknown; they are not confirmed to be within the cap.
`passengers`	No	Number of passengers
`destination`	No	Arrival city or airport code (e.g. "Las Vegas" or "KLAS")
`departureDateTo`	No	Latest departure date in ISO format
`departureDateFrom`	No	Earliest departure date in ISO format (e.g. "2026-07-10")

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 2, 2026

changedInput schema / properties / max_price / description

Previous value: -"Optional price ceiling in USD (all-in customer price). Legs priced above this figure are excluded. Legs with no published price (price: null, shown as \"Contact for price\") are still included because their price is unknown; they are not confirmed to be within the cap."New value: +"Optional price ceiling in USD (whole-aircraft price; taxes and fees shown at checkout). Legs priced above this figure are excluded. Legs with no published price (price: null, shown as \"Contact for price\") are still included because their price is unknown; they are not confirmed to be within the cap."

Changed1 schema field changedSep 30, 2026

changedInput schema / properties / max_price / description

Previous value: -"Optional price ceiling in USD (all-in customer price). Only legs at or below this figure are returned. One exception, by design: legs whose operator has not confirmed they will honour a published price are still returned regardless of the cap, with `price: null` — describe those as \"Contact for price\" and do NOT tell the customer they fall within the cap, because their price is unknown, not low."New value: +"Optional price ceiling in USD (all-in customer price). Legs priced above this figure are excluded. Legs with no published price (price: null, shown as \"Contact for price\") are still included because their price is unknown; they are not confirmed to be within the cap."

First observedSep 6, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive behavior, so the description correctly focuses on what the annotations cannot convey: the 5-result cap, the returned fields, and the important edge case that price:null legs are included even when max_price is set and are not confirmed within the cap. This is genuinely useful behavioral context beyond the structured fields.

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-loads the search dimensions, then the return shape, then the domain and edge-case explanation. Every sentence carries information, though the null-price caveat appears twice (description and schema) and could be tightened.

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 correctly carries the burden of describing return values (route, departure time, price, aircraft type, seats, booking link) and the semantics of empty legs and null prices. An agent has what it needs to search and interpret results, though it does not clarify whether all parameters are optional or how the empty result set is surfaced.

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 coverage is 100%, so each parameter is already documented with format examples and the max_price null-price nuance. The description largely restates the schema's own parameter notes (origin, destination, dates, passengers, max_price), so it adds little beyond the schema baseline.

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 (Search) plus resource (empty leg flights) and enumerates the search dimensions. It is clearly distinguished from siblings like get_flight and request_booking, which are lookup and mutation tools respectively.

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

Usage Guidelines3/5

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

Usage is implied: this is the tool to search discounted private jet availability on specific routes. However, there is no explicit statement of when to prefer this over siblings such as get_flight or get_charter_estimate, nor any exclusions or prerequisites.

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

All SkyAccess 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.