Skip to main content
Glama

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.

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": {
      "email": "<email>"
    },
    "name": "create_flight_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesThe user's email address.
localeNoLanguage of texts and links in the result: en or de.en
originNoDeparture city, IATA/ICAO code, country, US state, region or area.
date_toNoLatest departure date to watch (YYYY-MM-DD).
date_fromNoEarliest departure date to watch (YYYY-MM-DD).
passengersNoNumber of passengers; only offers with at least this many seats.
destinationNoArrival city, IATA/ICAO code, country, US state, region or area.
max_price_eurNoMaximum price in EUR for the whole aircraft.
aircraft_classNoOnly these aircraft classes. Offers without a known aircraft type are excluded.

Output Schema

NameRequiredDescriptionDefault
statusYes
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / date_from / description
      Added value: +"Earliest departure date to watch (YYYY-MM-DD)."
    • addedInput schema / properties / date_to / description
      Added value: +"Latest departure date to watch (YYYY-MM-DD)."
    • addedInput schema / properties / locale / description
      Added value: +"Language of texts and links in the result: en or de."
    • addedInput schema / properties / max_price_eur / description
      Added value: +"Maximum price in EUR for the whole aircraft."
    • addedInput schema / properties / passengers / description
      Added value: +"Number of passengers; only offers with at least this many seats."
  2. Changed2 schema fields changed
    • 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."
  3. Changed1 schema field changed
    • 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"
      +}
  4. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the full lifecycle: an email with a confirmation link is sent, the alert stays inactive until the user clicks, double opt-in, and the link expires in 7 days. That is exactly the non-obvious side effect an agent needs to warn the user about before calling.

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, front-loaded with the action and the trigger, then the opt-in consequence, then the constraint summary. No filler or restated field definitions.

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 9 parameters, an output schema and annotations already covering the safety profile, the description covers the essential behavior and requirement. It omits any mention of the locale parameter's effect on alert language, though the schema documents that adequately.

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 coverage is 100%, so the baseline is 3, but the description adds a cross-field constraint the schema cannot express: origin or destination must be supplied despite only email being required. It also marks dates, passengers and budget as optional, which is useful framing beyond per-field docs.

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 two scoping modes (route or place). An agent can distinguish this from search_empty_legs because the description frames it as a persistent alert rather than a query.

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 a clear trigger condition: 'for when the user asks to be notified and gives their email', and states the data requirement ('Needs origin or destination'). It stops short of naming a sibling alternative such as search_empty_legs for one-off lookups, so it is clear but not fully exclusionary.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources