SlickTrip

Add a flight bucket list

add_flight_bucket_list

Idempotent

Use for flexible-date watches ('tell me when New York to Tokyo drops under $700 this winter'): SlickTrip keeps searching the chosen months or date window and alerts when a fare clears the price bar. Returns a bucket_id. Confirm first. Not for fixed dates (search_flights, then track_flight).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	No	A 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.
`cabin`	No	Cabin class.	economy
`months`	No	Months to watch, as names or YYYY-MM. Give this OR start_date + end_date.
`origin`	Yes	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.
`airlines`	No	Only these marketing carriers, as IATA codes or names.
`end_date`	No	Last travel date, YYYY-MM-DD.
`max_stops`	No	Most stops allowed: 0 nonstop, 1, or 2.
`travelers`	No	Travelers. Fares are quoted for all of them together; one booking holds up to 9 (a larger group gets a suggested split).
`trip_type`	No	Round trip or one way.	roundtrip
`max_nights`	No	Longest trip, nights (round trips).
`min_nights`	No	Shortest trip, nights (round trips).
`start_date`	No	First travel date, YYYY-MM-DD. Give with end_date instead of months.
`depart_days`	No	Only depart on these weekdays.
`destination`	Yes	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.
`return_days`	No	Only return on these weekdays.
`user_request`	No	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.
`max_price_usd`	No	The price bar, USD per traveler (or the trip total when price_is_total).
`price_is_total`	No	max_price_usd is the total for all travelers.

Output Schema

TableJSON Schema

Name	Required	Description
`code`	No	On an error: a machine-readable kind, e.g. unknown_place
`kind`	No	Always "flight"
`name`	No	Custom name if given
`note`	No	First results timing
`field`	No	On unknown_place: which argument (origin, destination, ...)
`route`	No	origin, destination, names, destination_image, trip_type, cabin, travelers
`alerts`	No	Plain-words description of alerts
`months`	No	Month names watched
`nights`	No	[min_nights, max_nights] for round trips
`status`	No	watching \| error \| sign_in_required
`window`	No	{start, end} date window
`message`	No	Error or sign-in message from the server wrapper
`airlines`	No	IATA carrier codes
`channels`	No	Alert channels on the record: email, text (booleans)
`bucket_id`	No	The new bucket list record id
`max_stops`	No	Stop limit 0-2
`saved_url`	No	slicktrip.com saved-buckets page link
`handoff_url`	No	Bucket-list autosave link on slicktrip.com
`suggestions`	No	On unknown_place: places to offer the traveler, each with code, name, kind (airport, all airports in the city, nearby airport), city, country
`display_name`	No	Name as the card shows it
`max_price_usd`	No	Price bar
`places_assumed`	No	Place names this call resolved on its own, e.g. 'Portland = Portland, OR (PDX)'; tell the traveler

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 6, 2026

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

First observedOct 5, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is largely covered. The description adds real behavioral context beyond that: the watch keeps searching and alerts when the fare clears the bar, a bucket_id is returned, and confirmation is required before creating. It doesn't cover how alerts are delivered or any limits on concurrent watches.

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 exact use case and example, followed by the return value, the confirmation requirement, and the exclusion. No filler; every clause carries routing or behavioral information.

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 an 18-parameter creation tool with a full-coverage schema and an output schema (so return values need not be explained), the description covers the core intent, the alternative path for fixed dates, and the confirmation step. It is a little thin on what happens after creation (alert cadence, output schema fields like bucket_id aside), but nothing essential to calling it correctly is missing.

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 description coverage is 100%, so all 18 parameters are already documented in the schema, including months vs start_date/end_date and the price bar. The description only gestures at the flexible-date window and price bar, adding no syntax or format detail beyond what the schema provides, so the baseline 3 applies.

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?

The description gives a concrete verb+resource ('flexible-date watches' / bucket list) and grounds it with a realistic example ('tell me when New York to Tokyo drops under $700 this winter'). It explicitly names the siblings it is not for (search_flights, track_flight with fixed dates), so an agent can distinguish it without opening any 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?

States when to use it (flexible dates, price-bar alerts over months or a date window), when not to (fixed dates go to search_flights then track_flight), and adds an operational prerequisite ('Confirm first'). Both routing conditions and the alternative path are explicit.

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

All SlickTrip 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?