SlickTrip

Link into SlickTrip

handoff_link

Read-onlyIdempotent

Use when the traveler wants to continue on slicktrip.com, or the account is not connected: builds a link that lands them fully configured without running a search (a flights search with a track_url that starts tracking on arrival, a bucket list that saves on arrival, a hotel search, or the seat tracker).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`kind`	Yes	Which page to land on.
`legs`	No	Multi-city trip: the legs in order, 2 to 5, each one airport or city code per side and one date. When given, origin / destination / depart_date / return_date are ignored.
`cabin`	No	Cabin class; several joined with + to compare them (economy+business).	economy
`adults`	No	Adults. A hotel room prices up to 6 guests in all; vacation rentals up to 16.
`months`	No	Months to watch, as names or YYYY-MM. Give this OR start_date + end_date.
`origin`	No	A 3-letter airport code (JFK) or a city code for all its airports (NYCA, LOND, ROME); up to 3 joined with _ (JFK_EWR). A clear place name works too. Unsure of the code: call find_places.
`airlines`	No	Only these marketing carriers, as IATA codes or names.
`check_in`	No	YYYY-MM-DD.
`end_date`	No	YYYY-MM-DD.
`hotel_id`	No	hotels: open this one hotel from search_hotels.
`location`	No	hotels: a city, area, landmark or hotel name.
`check_out`	No	YYYY-MM-DD.
`max_stops`	No	Most stops allowed: 0 nonstop, 1, or 2.
`min_stars`	No	Lowest star class to show, 1-5.
`travelers`	No	Travelers. Fares are quoted for all of them together; one booking holds up to 9 (a larger group gets a suggested split).
`max_nights`	No	Nights, 1-30.
`min_nights`	No	Nights, 1-30.
`start_date`	No	YYYY-MM-DD.
`depart_date`	No	YYYY-MM-DD. A second date joined with _ searches both as flexible dates (2026-11-03_2026-11-04); at most 2 per direction.
`destination`	No	A 3-letter airport code (JFK) or a city code for all its airports (NYCA, LOND, ROME); up to 3 joined with _ (JFK_EWR). A clear place name works too. Unsure of the code: call find_places.
`return_date`	No	YYYY-MM-DD.
`children_ages`	No	One age per child, 1-17.
`flight_number`	No	seats: the flight to open in the seat tracker.
`max_price_usd`	No	bucket_list: the price bar, USD.
`flight_numbers`	No	flights: the itinerary's flight numbers, connections joined with +; adds a track_url that starts tracking on arrival.
`max_price_per_night`	No	Highest price per night to show, USD.

Output Schema

TableJSON Schema

Name	Required	Description
`url`	No	The slicktrip.com landing link
`code`	No	On an error: a machine-readable kind, e.g. unknown_place
`kind`	No	flights \| bucket_list \| hotels \| seats
`note`	No	What the links do on arrival
`field`	No	On unknown_place: which argument (origin, destination, ...)
`status`	No	error \| sign_in_required (absent on success)
`message`	No	Error or sign-in message from the server wrapper
`setup_url`	No	seats with flight_number: seat setup page link
`track_url`	No	flights with flight_numbers: autosave tracking link
`search_key`	No	flights/hotels: the search key built
`prefill_url`	No	bucket_list: form pre-filled, not saved
`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
`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.

Changed8 schema fields changedOct 6, 2026

changedInput schema / $defs / Leg / 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 / $defs / Leg / properties / destination / examples

Previous value: -[
-  "JFK",
-  "ROM",
-  "JFK_EWR"
-]New value: +[
+  "JFK",
+  "NYCA",
+  "JFK_EWR"
+]

changedInput schema / $defs / Leg / 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 / $defs / Leg / properties / origin / examples

Previous value: -[
-  "JFK",
-  "ROM",
-  "JFK_EWR"
-]New value: +[
+  "JFK",
+  "NYCA",
+  "JFK_EWR"
+]

changedInput schema / properties / destination / description

Previous value: -"A 3-letter airport code (JFK) or a city code for all its airports (NYC, LON, ROM); up to 3 joined with _ (JFK_EWR). A clear place name works too. Unsure of the code: call find_places."New value: +"A 3-letter airport code (JFK) or a city code for all its airports (NYCA, LOND, ROME); up to 3 joined with _ (JFK_EWR). A clear place name works too. 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 for all its airports (NYC, LON, ROM); up to 3 joined with _ (JFK_EWR). A clear place name works too. Unsure of the code: call find_places."New value: +"A 3-letter airport code (JFK) or a city code for all its airports (NYCA, LOND, ROME); up to 3 joined with _ (JFK_EWR). A clear place name works too. 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.3/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so the safety profile is covered. The description adds real context beyond them: the link lands the user 'without running a search', the track_url 'starts tracking on arrival', and the bucket list 'saves on arrival' — side effects on the destination site. It does not explain link expiry or auth requirements in detail, hence 4 rather than 5.

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?

A single dense sentence, but front-loaded with the usage condition and then the behavior, so an agent reads the decisive information first. It is longer than ideal and the parenthetical enumeration is heavy, but every clause carries signal.

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 26 parameters, a 100%-covered schema, and an output schema present, the description only needs to cover purpose, trigger, and the net effect of the link. It does all three, so the definition is complete enough to call correctly; minor gaps around what the returned link looks like are covered by the output schema.

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 100%, so the baseline is 3, but the description genuinely adds meaning the schema lacks: the `kind` enum is only described as 'Which page to land on' in the schema, while the description explains what each kind produces (a configured flights search, a saved bucket list, etc.). That mapping is not recoverable from the schema alone.

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 states a specific verb and resource ('builds a link that lands them fully configured') and enumerates exactly what the link can target, matching the four values of the `kind` enum: flights search, bucket list, hotel search, seat tracker. An agent can distinguish this from siblings such as share_link or track_flight 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 Guidelines4/5

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

It gives an explicit triggering condition: 'Use when the traveler wants to continue on slicktrip.com, or the account is not connected.' That is clear when-to-use guidance. It stops short of naming alternatives or when-not (e.g., when the account IS connected and an in-app search is preferred), so it is not a full 5.

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?