Mirai Flights

Search empty legs

search_empty_legs

Read-only

Searches empty leg flights: discounted one-way repositioning flights that depart within a time window. All filters are optional. Each result has id and company_id for get_empty_leg.

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
`pax`	No	group size; listed prices are minimums per jet, get_empty_leg prices the group
`page`	No
`sort`	No	departure_date or price, ascending
`to_ref`	No	ref from find_location
`date_to`	No	YYYY-MM-DD
`currency`	No	currency the user asked for; default EUR, follow-ups keep the search currency
`from_ref`	No	ref from find_location
`language`	No	response language; defaults to the client's Accept-Language, then en
`date_from`	No	YYYY-MM-DD
`price_max`	No
`price_min`	No
`aircraft_class_ids`	No	ids from list_aircraft_classes

Output Schema

Name	Required	Description
`pax`	No	passengers the search was for
`page`	Yes
`currency`	Yes	pass the same currency to get_empty_leg
`empty_legs`	Yes
`total_pages`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 12, 2026

addedInput schema / properties / pax / description

Added value: +"group size; listed prices are minimums per jet, get_empty_leg prices the group"

addedOutput schema / properties / currency

Added value: +{
+  "description": "pass the same currency to get_empty_leg",
+  "type": "string"
+}

addedOutput schema / properties / empty_legs / items / properties / from_city
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / empty_legs / items / properties / to_city
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / pax

Added value: +{
+  "description": "passengers the search was for",
+  "type": "integer"
+}

changedOutput schema / required

Previous value: -[
-  "empty_legs",
-  "page",
-  "total_pages"
-]New value: +[
+  "empty_legs",
+  "page",
+  "total_pages",
+  "currency"
+]

Changed2 schema fields changedNov 12, 2026

addedOutput schema / properties / empty_legs / items / properties / image

Added value: +{
+  "description": "destination photo URL",
+  "type": "string"
+}

addedOutput schema / properties / empty_legs / items / properties / photos

Added value: +{
+  "description": "aircraft and cabin photo URLs",
+  "items": {
+    "type": "string"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}

First observedNov 12, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare read-only, open-world, non-idempotent, and non-destructive behavior, so the bar is lower. Beyond that, the description adds real context: listed prices are minimums per jet and get_empty_leg prices the actual group, plus each result carries id and company_id for follow-up. Pagination behavior for the page parameter is not described, keeping it from a 5.

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?

Two tightly written sentences with the definition front-loaded and the follow-up handoff second. No redundant restatement of the name or annotations, and nothing extraneous.

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 a 12-parameter, zero-required search tool with an output schema and full annotations, the description covers the domain definition, the optional-filter nature, and the result-to-get_empty_leg workflow. Return values need not be explained because an output schema exists; only the absence of explicit alternative-tool guidance is a gap.

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 75%, so most parameters (currency defaults, language fallback, ref provenance, date formats) are already documented in the schema. The description only adds that every filter is optional, which is a useful but minimal semantic contribution beyond the structured fields.

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 and resource ("Searches empty leg flights") and immediately defines the resource domain as discounted one-way repositioning flights departing within a time window. The mention of result ids and the get_empty_leg handoff further pins down what this tool returns, so an agent can distinguish it from generic charter searches.

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?

Conveys that all filters are optional and that results feed into get_empty_leg for pricing, which is useful next-step guidance. However, it never explains when to choose this over search_charter or another sibling, so the main when-to-use decision is left implicit.

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

All Mirai Flights 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.