Skip to main content
Glama

Add a flight bucket list

add_flight_bucket_list
Idempotent

Call this tool when the traveler wants to be alerted about a route over flexible dates, for example "tell me when New York to Tokyo drops under $700 this winter". SlickTrip keeps searching the months or dates the traveler chose and alerts them when a fare is under their price limit. It returns a bucket_id.

When the traveler asks to be alerted, call it now: that is their go-ahead. Otherwise offer it first.

Use the months, the number of nights and the price limit the traveler gave you, and the defaults for anything they did not say (every month on sale, 3 to 10 nights, 1 traveler); then tell them what you assumed. They can change any of it with update_bucket_list.

Do not use this tool for fixed dates. Search those dates with search_flights, then use track_flight to watch the flight the traveler picks.

Input Schema

NameRequiredDescriptionDefault
nameNoA short name for the list in the traveler's words; give one. It is how the list is called in every alert and on the site.
cabinNoCabin class.economy
monthsNoMonths to watch, as names or YYYY-MM, or give start_date + end_date. Leave both empty to watch every month on sale (the default).
originYesA 3-letter airport code (JFK), or a city code that searches every airport in the city (SlickTrip's 4-letter codes: NYCA New York, LOND London, ROME Rome, TYOA Tokyo). Up to 3 places joined with _ search them together (JFK_EWR). A place name works when one place clearly matches; otherwise the result is an unknown_place error listing suggestions. When the traveler names a city rather than an airport, send the city (its name or code), not one of its airports: one airport can miss the cheapest or the only flights. Unsure of the code: call find_places.
airlinesNoOnly these marketing carriers, as IATA codes or names.
end_dateNoLast travel date, YYYY-MM-DD.
max_stopsNoMost stops allowed: 0 nonstop, 1, or 2.
travelersNoTravelers who need a seat (adults and children). Fares are quoted for all of them together; one booking holds up to 9 (a larger group gets a suggested split). A baby under 2 on a lap is not a seat and is not counted here.
trip_typeNoRound trip or one way.roundtrip
max_nightsNoLongest trip, nights (round trips).
min_nightsNoShortest trip, nights (round trips).
start_dateNoFirst travel date, YYYY-MM-DD. Give with end_date instead of months.
depart_daysNoOnly depart on these weekdays.
destinationYesA 3-letter airport code (JFK), or a city code that searches every airport in the city (SlickTrip's 4-letter codes: NYCA New York, LOND London, ROME Rome, TYOA Tokyo). Up to 3 places joined with _ search them together (JFK_EWR). A place name works when one place clearly matches; otherwise the result is an unknown_place error listing suggestions. When the traveler names a city rather than an airport, send the city (its name or code), not one of its airports: one airport can miss the cheapest or the only flights. Unsure of the code: call find_places.
return_daysNoOnly return on these weekdays.
arrive_afterNoHH:MM, local time at that airport.
checked_bagsNoChecked bags per traveler (0-2), priced only for flights within the US and Canada (elsewhere the answer says the prices do not include them). Prices then include the bag fees: search_flights shows them as price_with_bags next to the fare; a calendar or bucket list prices every day with them.
depart_afterNoHH:MM, local time at that airport.
user_requestNoOptional, and it works in the traveler's favor. Quote the traveler's latest message about this trip exactly as they wrote it, in their wording, language and spelling, not a summary. SlickTrip runs its own travel parser on these words: when a search fails or comes back empty, it compares what the traveler said with the arguments sent and returns a corrected search, so you can fix it without asking them again. It has caught Cancun sent as MEX instead of CUN, and travelers dropped from the party. A summary loses exactly the details it checks. If the message only answers a question ("yes, the 20th"), quote the message where they asked for the trip. Send the same quote on every call for this request. Leave out anything not about the trip, and never include names, contact details, or payment or ID information. The words also help SlickTrip improve its search.
arrive_beforeNoHH:MM, local time at that airport.
carry_on_bagsNoCarry-on bags per traveler (0-1). Prices then include the bag fees: search_flights shows them as price_with_bags next to the fare; a calendar or bucket list prices every day with them.
depart_beforeNoHH:MM, local time at that airport.
max_price_usdNoThe price bar, USD per traveler (or the trip total when price_is_total).
price_is_totalNomax_price_usd is the total for all travelers.
lower_emissionsNoOnly itineraries with lower emissions than is typical for the route.
exclude_airlinesNoLeave out itineraries with any flight sold by these carriers (IATA codes, names or an alliance), by flight number or airline name: for 'not Gol' or 'avoid Air India'.
max_layover_hoursNoLongest layover allowed at every connection, in hours (half hours allowed): for 'layovers no longer than 5 hours'.
min_layover_hoursNoShortest layover allowed at every connection, in hours (half hours allowed): for 'at least 2 hours to connect'.
max_duration_hoursNoLongest itinerary to show, in hours.
connecting_airportsNoOnly itineraries that change planes at these airports (codes or city codes), nonstops included: for 'US connections only' name the hubs.
exclude_connecting_airportsNoLeave out itineraries that change planes at these airports (codes or city codes).

Output Schema

NameRequiredDescriptionDefault
codeNoOn an error: a machine-readable kind, e.g. unknown_place
kindNoAlways "flight"
nameNoCustom name if given
noteNoFirst results timing
fieldNoOn unknown_place: which argument (origin, destination, ...)
routeNoorigin, destination, names, destination_image, trip_type, cabin, travelers
alertsNoPlain-words description of alerts
monthsNoMonth names watched
nightsNo[min_nights, max_nights] for round trips
statusNowatching | error | sign_in_required
windowNo{start, end} date window
messageNoError or sign-in message from the server wrapper
airlinesNoIATA carrier codes
channelsNoAlert channels on the record: email, text (booleans)
bucket_idNoThe new bucket list record id
max_stopsNoStop limit 0-2
saved_urlNoslicktrip.com saved-buckets page link
handoff_urlNoBucket-list autosave link on slicktrip.com
suggestionsNoOn unknown_place: places to offer the traveler, each with code, name, kind (airport, all airports in the city, nearby airport), city, country
display_nameNoName as the card shows it
max_price_usdNoPrice bar
places_assumedNoPlace names this call resolved on its own, e.g. 'Portland = Portland, OR (PDX)'; tell the traveler

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / checked_bags / description
      Previous value: -"Checked bags per traveler (0-2). Prices then include the bag fees: search_flights shows them as price_with_bags next to the fare; a calendar or bucket list prices every day with them."New value: +"Checked bags per traveler (0-2), priced only for flights within the US and Canada (elsewhere the answer says the prices do not include them). Prices then include the bag fees: search_flights shows them as price_with_bags next to the fare; a calendar or bucket list prices every day with them."
  2. Changed13 schema fields changed
    • addedInput schema / properties / arrive_after
      Added value: +{
      +  "anyOf": [
      +    {
      +      "pattern": "^\\d{2}:\\d{2}$",
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "HH:MM, local time at that airport.",
      +  "examples": [
      +    "06:00",
      +    "21:30"
      +  ],
      +  "title": "Arrive After"
      +}
    • addedInput schema / properties / arrive_before
      Added value: +{
      +  "anyOf": [
      +    {
      +      "pattern": "^\\d{2}:\\d{2}$",
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "HH:MM, local time at that airport.",
      +  "examples": [
      +    "06:00",
      +    "21:30"
      +  ],
      +  "title": "Arrive Before"
      +}
    • addedInput schema / properties / carry_on_bags
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maximum": 1,
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Carry-on bags per traveler (0-1). Prices then include the bag fees: search_flights shows them as price_with_bags next to the fare; a calendar or bucket list prices every day with them.",
      +  "title": "Carry On Bags"
      +}
    • addedInput schema / properties / checked_bags
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maximum": 2,
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Checked bags per traveler (0-2). Prices then include the bag fees: search_flights shows them as price_with_bags next to the fare; a calendar or bucket list prices every day with them.",
      +  "title": "Checked Bags"
      +}
    • addedInput schema / properties / connecting_airports
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Only itineraries that change planes at these airports (codes or city codes), nonstops included: for 'US connections only' name the hubs.",
      +  "examples": [
      +    [
      +      "MIA",
      +      "ATL",
      +      "IAH"
      +    ]
      +  ],
      +  "title": "Connecting Airports"
      +}
    • addedInput schema / properties / depart_after
      Added value: +{
      +  "anyOf": [
      +    {
      +      "pattern": "^\\d{2}:\\d{2}$",
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "HH:MM, local time at that airport.",
      +  "examples": [
      +    "06:00",
      +    "21:30"
      +  ],
      +  "title": "Depart After"
      +}
    • addedInput schema / properties / depart_before
      Added value: +{
      +  "anyOf": [
      +    {
      +      "pattern": "^\\d{2}:\\d{2}$",
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "HH:MM, local time at that airport.",
      +  "examples": [
      +    "06:00",
      +    "21:30"
      +  ],
      +  "title": "Depart Before"
      +}
    • addedInput schema / properties / exclude_airlines
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Leave out itineraries with any flight sold by these carriers (IATA codes, names or an alliance), by flight number or airline name: for 'not Gol' or 'avoid Air India'.",
      +  "examples": [
      +    [
      +      "G3"
      +    ],
      +    [
      +      "Gulf Air",
      +      "Air India"
      +    ]
      +  ],
      +  "title": "Exclude Airlines"
      +}
    • addedInput schema / properties / exclude_connecting_airports
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Leave out itineraries that change planes at these airports (codes or city codes).",
      +  "examples": [
      +    [
      +      "DOH"
      +    ],
      +    [
      +      "LOND"
      +    ]
      +  ],
      +  "title": "Exclude Connecting Airports"
      +}
    • addedInput schema / properties / lower_emissions
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Only itineraries with lower emissions than is typical for the route.",
      +  "title": "Lower Emissions"
      +}
    • addedInput schema / properties / max_duration_hours
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maximum": 96,
      +      "minimum": 1,
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Longest itinerary to show, in hours.",
      +  "title": "Max Duration Hours"
      +}
    • addedInput schema / properties / max_layover_hours
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maximum": 26,
      +      "minimum": 0.5,
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Longest layover allowed at every connection, in hours (half hours allowed): for 'layovers no longer than 5 hours'.",
      +  "title": "Max Layover Hours"
      +}
    • addedInput schema / properties / min_layover_hours
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maximum": 26,
      +      "minimum": 0.5,
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Shortest layover allowed at every connection, in hours (half hours allowed): for 'at least 2 hours to connect'.",
      +  "title": "Min Layover Hours"
      +}
  3. Changed7 schema fields changed
    • changedInput schema / properties / destination / description
      Previous value: -"A 3-letter airport code (JFK), or a city code that searches every airport in the city (SlickTrip's 4-letter codes: NYCA New York, LOND London, ROME Rome, TYOA Tokyo). Up to 3 places joined with _ search them together (JFK_EWR). A place name works when one place clearly matches; otherwise the result is an unknown_place error listing suggestions. Unsure of the code: call find_places."New value: +"A 3-letter airport code (JFK), or a city code that searches every airport in the city (SlickTrip's 4-letter codes: NYCA New York, LOND London, ROME Rome, TYOA Tokyo). Up to 3 places joined with _ search them together (JFK_EWR). A place name works when one place clearly matches; otherwise the result is an unknown_place error listing suggestions. When the traveler names a city rather than an airport, send the city (its name or code), not one of its airports: one airport can miss the cheapest or the only flights. Unsure of the code: call find_places."
    • changedInput schema / properties / months / description
      Previous value: -"Months to watch, as names or YYYY-MM. Give this OR start_date + end_date."New value: +"Months to watch, as names or YYYY-MM, or give start_date + end_date. Leave both empty to watch every month on sale (the default)."
    • changedInput schema / properties / origin / description
      Previous value: -"A 3-letter airport code (JFK), or a city code that searches every airport in the city (SlickTrip's 4-letter codes: NYCA New York, LOND London, ROME Rome, TYOA Tokyo). Up to 3 places joined with _ search them together (JFK_EWR). A place name works when one place clearly matches; otherwise the result is an unknown_place error listing suggestions. Unsure of the code: call find_places."New value: +"A 3-letter airport code (JFK), or a city code that searches every airport in the city (SlickTrip's 4-letter codes: NYCA New York, LOND London, ROME Rome, TYOA Tokyo). Up to 3 places joined with _ search them together (JFK_EWR). A place name works when one place clearly matches; otherwise the result is an unknown_place error listing suggestions. When the traveler names a city rather than an airport, send the city (its name or code), not one of its airports: one airport can miss the cheapest or the only flights. Unsure of the code: call find_places."
    • changedInput schema / properties / travelers / description
      Previous value: -"Travelers. Fares are quoted for all of them together; one booking holds up to 9 (a larger group gets a suggested split)."New value: +"Travelers who need a seat (adults and children). Fares are quoted for all of them together; one booking holds up to 9 (a larger group gets a suggested split). A baby under 2 on a lap is not a seat and is not counted here."
    • changedInput schema / properties / user_request / anyOf
      Previous value: -[
      -  {
      -    "maxLength": 300,
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "maxLength": 500,
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / user_request / description
      Previous value: -"Optional. The traveler's current travel request, briefly, in their own words. Used to interpret this search, suggest a corrected search if it fails, and improve SlickTrip's search. Include only this request; not earlier conversation, names, contact details, or payment or ID information."New value: +"Optional, and it works in the traveler's favor. Quote the traveler's latest message about this trip exactly as they wrote it, in their wording, language and spelling, not a summary. SlickTrip runs its own travel parser on these words: when a search fails or comes back empty, it compares what the traveler said with the arguments sent and returns a corrected search, so you can fix it without asking them again. It has caught Cancun sent as MEX instead of CUN, and travelers dropped from the party. A summary loses exactly the details it checks. If the message only answers a question (\"yes, the 20th\"), quote the message where they asked for the trip. Send the same quote on every call for this request. Leave out anything not about the trip, and never include names, contact details, or payment or ID information. The words also help SlickTrip improve its search."
    • changedInput schema / properties / user_request / examples
      Previous value: -[
      -  "cheap nonstop to Lisbon early May",
      -  "family of 8 in Albufeira, 4 nights mid November"
      -]New value: +[
      +  "we're 6 friends from madrid, want somewhere cheap and fun in europe dec 20-24, morning flights pls",
      +  "necesito llevar a mi mamá de Calgary a Kolkata a fines de octubre, no puede hacer escala en Estados Unidos"
      +]
  4. Changed4 schema fields changed
    • changedInput schema / properties / destination / description
      Previous value: -"A 3-letter airport code (JFK), or a city code that searches every airport in the city (NYC, LON, ROM, TYO). Up to 3 airports joined with _ search them together (JFK_EWR). A place name works when one place clearly matches; otherwise the result is an unknown_place error listing suggestions. Unsure of the code: call find_places."New value: +"A 3-letter airport code (JFK), or a city code that searches every airport in the city (SlickTrip's 4-letter codes: NYCA New York, LOND London, ROME Rome, TYOA Tokyo). Up to 3 places joined with _ search them together (JFK_EWR). A place name works when one place clearly matches; otherwise the result is an unknown_place error listing suggestions. Unsure of the code: call find_places."
    • changedInput schema / properties / destination / examples
      Previous value: -[
      -  "JFK",
      -  "ROM",
      -  "JFK_EWR"
      -]New value: +[
      +  "JFK",
      +  "NYCA",
      +  "JFK_EWR"
      +]
    • changedInput schema / properties / origin / description
      Previous value: -"A 3-letter airport code (JFK), or a city code that searches every airport in the city (NYC, LON, ROM, TYO). Up to 3 airports joined with _ search them together (JFK_EWR). A place name works when one place clearly matches; otherwise the result is an unknown_place error listing suggestions. Unsure of the code: call find_places."New value: +"A 3-letter airport code (JFK), or a city code that searches every airport in the city (SlickTrip's 4-letter codes: NYCA New York, LOND London, ROME Rome, TYOA Tokyo). Up to 3 places joined with _ search them together (JFK_EWR). A place name works when one place clearly matches; otherwise the result is an unknown_place error listing suggestions. Unsure of the code: call find_places."
    • changedInput schema / properties / origin / examples
      Previous value: -[
      -  "JFK",
      -  "ROM",
      -  "JFK_EWR"
      -]New value: +[
      +  "JFK",
      +  "NYCA",
      +  "JFK_EWR"
      +]
  5. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive. The description adds real context beyond them: the list keeps searching and alerts when a fare drops under the limit, the tool returns a bucket_id, sensible defaults are applied and should be surfaced to the traveler, and the list can later be changed via update_bucket_list. It does not mention cost, rate limits, or alert frequency, which keeps it short of 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?

Four short paragraphs, each earning its place: trigger and effect, call-vs-offer rule, defaults policy, and the exclusion/alternative. Front-loaded with the caller's situation and example, with no filler.

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

Completeness5/5

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

For a 31-parameter mutation tool with full schema coverage and an output schema, the description covers everything an agent needs: when to call, what it produces (bucket_id), what defaults to use, how to revise later, and which siblings handle the cases this tool does not.

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. The description adds policy-level guidance the schema cannot: use what the traveler gave, fill the rest with defaults (every month on sale, 3-10 nights, 1 traveler) and tell them what was assumed. It does not walk through individual parameters, which is fine given the rich schema.

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 (creates a bucket list that watches a route and alerts on price drops) and gives a concrete example request. It also distinguishes itself from search_flights, track_flight, and update_bucket_list by name, so an agent can route correctly without opening another schema.

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

Usage Guidelines5/5

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

Explicit when-to-use (traveler wants alerts over flexible dates, and even 'call it now' vs 'offer it first' depending on whether they asked), and explicit when-not-to-use (fixed dates go to search_flights then track_flight). Alternatives are named with the condition that selects them.

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