voidjet empty legs

Set up a flight alert

create_flight_alert

Idempotent

Sets up an email alert for new empty legs on a route or from a place, for when the user asks to be notified and gives their email. voidjet emails a confirmation link; the alert becomes active only after the user clicks it (double opt-in, valid 7 days). Needs origin or destination; dates, passengers and budget are optional.

Input Schema

Name	Required	Description	Default
`email`	Yes	The user's email address.
`locale`	No		en
`origin`	No	Departure city, IATA/ICAO code, country, US state, region or area.
`date_to`	No
`date_from`	No
`passengers`	No
`destination`	No	Arrival city, IATA/ICAO code, country, US state, region or area.
`max_price_eur`	No
`aircraft_class`	No	Only these aircraft classes. Offers without a known aircraft type are excluded.

Output Schema

Name	Required	Description	Default
`status`	Yes
`message`	Yes

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."New value: +"Departure city, IATA/ICAO code, country, US state, region or area."

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

AddedOct 10, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), so the description's value is in the workflow detail it adds: voidjet sends a confirmation link and the alert is only active after the user clicks it, with a 7-day opt-in window. That double opt-in requirement is meaningful behavior an agent must convey to the user and is not captured by annotations.

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 tight sentences with the purpose first, then the confirmation workflow, then the parameter constraints. Every sentence carries new information and nothing is repeated from the title or schema.

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?

An output schema exists, so return values need no explanation, and the description covers the trigger, the opt-in lifecycle and the key parameter constraint. The gaps (locale and aircraft_class semantics, e.g. that offers with unknown aircraft types are excluded) are minor but real for a 9-parameter tool.

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?

Schema description coverage is only 44%, so the description must compensate, and it does partially: it adds the cross-field constraint 'needs origin or destination' that the schema cannot express (only email is required) and labels dates, passengers and budget as optional. It leaves locale and aircraft_class unmentioned, which is why it is not a 5.

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 ('Sets up an email alert for new empty legs') plus the scope (a route or from a place), which cleanly separates it from the read-oriented siblings search_empty_legs and get_empty_leg. An agent can identify the operation without opening the schema.

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 an explicit trigger: 'for when the user asks to be notified and gives their email,' which tells the agent when this tool applies. It does not name the alternative tools (e.g. search_empty_legs) or state when not to use it, so it stops short of full routing guidance.

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?