Mirai Flights

Get empty leg

get_empty_leg

Read-only

Returns details, the price for a given number of passengers and the booking link for one empty leg. Booking happens on mirai.flights or in the Mirai app.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>",
      "company_id": "<company_id>"
    },
    "name": "get_empty_leg"
  }
}

Input Schema

Name	Required	Description
`id`	Yes
`pax`	No	group size; the price depends on it, so pass it whenever known
`currency`	No	currency the user asked for; default EUR, follow-ups keep the search currency
`language`	No	response language; defaults to the client's Accept-Language, then en
`company_id`	Yes

Output Schema

Name	Required	Description
`id`	Yes
`to`	Yes
`from`	Yes
`link`	No	booking link for the user
`image`	No	destination photo URL
`seats`	Yes
`photos`	No	aircraft and cabin photo URLs
`status`	Yes
`to_city`	No
`from_city`	No
`company_id`	Yes
`price_from`	Yes
`flight_time`	Yes
`aircraft_type`	Yes
`price_for_pax`	No
`departure_window`	Yes	local time range the flight can depart in

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 12, 2026
- addedInput schema / properties / pax / description
```
Added value: +"group size; the price depends on it, so pass it whenever known"
```
- addedOutput schema / properties / from_city
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / to_city
```
Added value: +{
+  "type": "string"
+}
```

Changed2 schema fields changedNov 12, 2026

addedOutput schema / properties / image

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

addedOutput schema / properties / photos

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

First observedNov 12, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered structurally. The description adds genuinely useful context that the price varies with passenger count and that actual booking happens off-API on mirai.flights or the Mirai app, but says nothing about the openWorld/price-volatility implications or why idempotentHint is false.

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?

Two tight sentences, front-loaded with the returned payload. The second sentence about booking destination earns its place by telling the agent the tool is not the booking mechanism.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and the read-only nature is annotated. However, for a 5-parameter tool with an unexplained required company_id, the description leaves a real gap an agent must resolve elsewhere.

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 60%, and the description mostly restates what the schema already says (pax drives price). The required company_id is undocumented in both schema and description, and currency/language semantics are left entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: returns details, a price for a given passenger count, and a booking link for ONE empty leg. The singular 'one empty leg' implicitly distinguishes it from the sibling search_empty_legs, though the sibling is never named.

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 only implied – it is a single-record lookup keyed by id and company_id, so an agent can infer it follows a search. There is no explicit when-to-use vs search_empty_legs or explanation of prerequisites such as where id/company_id come from.

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.