SlickTrip

Track seats on a flight

track_seats

Idempotent

Use to start seat alerts on one flight, after the traveler confirms: named seats, or every seat of a kind (window, aisle, middle, any), optionally only when N seats open together in a row. Alerts go to the account's channels when a watched seat opens.

Input Schema

Name	Required	Description	Default
`text`	No	Send alerts by text message. Needs a verified phone on the SlickTrip account; empty keeps the account's setting.
`cabin`	No	Cabin to look at; any = every cabin on the flight.	economy
`email`	No	Send alerts by email. Empty keeps the account's setting.
`seats`	No	Seat numbers to watch.
`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. 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.
`seat_type`	No	Watch every open seat of this kind instead of naming seats.
`depart_date`	Yes	YYYY-MM-DD.
`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. 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.
`flight_number`	Yes	Airline code and number, no space.
`seats_together`	No	Alert only when this many seats are open together in one row, 2-6.

Output Schema

Name	Required	Description
`code`	No	On an error: a machine-readable kind, e.g. unknown_place
`note`	No	Manage on saved-seats page
`cabin`	No	Cabin tracked, or list when several
`field`	No	On unknown_place: which argument (origin, destination, ...)
`alerts`	No	Plain-words description of alerts
`flight`	No	flight_number, origin, destination, departure_time, arrival_time, aircraft, airline
`status`	No	tracking \| error \| sign_in_required
`message`	No	Error or sign-in message from the server wrapper
`tracked`	No	seats, seat_type, specific_seats, seats_together, open_now
`channels`	No	Alert channels on the record: email, text (booleans)
`saved_url`	No	slicktrip.com saved-seats page link
`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
`tracking_key`	No	Seat tracking key: route;departure_time;flight_number
`places_assumed`	No	Place names this call resolved on its own, e.g. 'Portland = Portland, OR (PDX)'; tell the traveler
`merged_with_existing`	No	Added to an existing seat alert

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 9, 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 (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 / 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."

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.1/5.0

Behavior4/5

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

Annotations already declare this is a write (readOnlyHint=false), non-destructive, and idempotent, so the safety profile is covered. The description adds real behavioral context beyond that: alerts are delivered to the account's channels only when a watched seat opens, and the call should follow traveler confirmation. It does not say how alerts are later modified or stopped.

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?

Two sentences, front-loaded with the action and scope, with the mode options and the alert-delivery outcome packed in without filler. Nothing restates the schema verbatim and every clause carries 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?

With an output schema present, return values need no explanation, and the annotations carry the mutation/idempotency profile. The description covers what gets created, the two watch modes, and where alerts land; it omits lifecycle details such as duplicate-alert behavior or how to stop/modify tracking, which sibling tools cover.

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 the semantic relationship the schema documents only field-by-field: 'named seats, or every seat of a kind', plus 'only when N seats open together in a row' clarifying seats_together as a conditional filter on the other two.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'start seat alerts on one flight', and enumerates the two watch modes (named seats vs. seat type). It is distinguishable from stop_tracking_seats/update_seat_tracking by the word 'start', but it never names those siblings to make the boundary explicit.

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?

'Use to start seat alerts on one flight, after the traveler confirms' gives a clear activation context and a prerequisite (traveler confirmation). It stops short of saying when NOT to use it or pointing to update_seat_tracking/list_tracked_seats for the adjacent tasks.

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?