SlickTrip

Seat availability

seat_availability

Read-onlyIdempotent

Use to see which seats are open right now on one flight (signed-in account: the live seat map is a paid lookup): open seat numbers by row, counts of window, aisle, middle and exit-row seats, and rows with two seats together. Needs the flight number, route and date. Then track_seats to be told when a seat opens. Not for prices.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`cabin`	No	Cabin to look at; any = every cabin on the flight.	economy
`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.
`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. Unsure of the code: call find_places.
`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.
`flight_number`	Yes	Airline code and number, no space.

Output Schema

TableJSON Schema

Name	Required	Description
`code`	No	On an error: a machine-readable kind, e.g. unknown_place
`note`	No	Use track_seats to be alerted
`cabin`	No	Cabin tier queried
`field`	No	On unknown_place: which argument (origin, destination, ...)
`counts`	No	seats, available, window, aisle, middle, exit_row, rows_with_2_together
`flight`	No	flight_number, origin, destination, departure_time, arrival_time, aircraft, airline
`status`	No	ok \| no_data \| error \| sign_in_required
`message`	No	No seat map explanation or wrapper error
`exit_rows`	No	Row numbers with exit-row seats
`seat_kinds`	No	Seat letter to window \| aisle \| middle
`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
`seat_map_svg`	No	url, view_box, aircraft, seats[] with x/y/w/h/status/kind
`seat_map_url`	No	slicktrip.com seat-tracker setup page link
`open_seat_ids`	No	Every open seat id in the cabin, space-separated
`places_assumed`	No	Place names this call resolved on its own, e.g. 'Portland = Portland, OR (PDX)'; tell the traveler
`taken_seat_ids`	No	Every taken seat id in the cabin, space-separated
`available_seats`	No	Items: seat, kind, exit_row (up to 80)
`seat_tracker_url`	No	slicktrip.com seat-tracker route link

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

Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, open-world), and the description adds material context beyond them: the live seat map is a paid lookup and requires a signed-in account. Auth and cost prerequisites are exactly the kind of disclosure annotations cannot convey.

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?

Front-loaded with the action ('Use to see...'), followed by a dense but useful output list and two short routing sentences. Every sentence earns its place, though the parenthetical about the paid lookup is slightly compressed.

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?

An output schema exists, so return values need not be re-explained, and the description still covers purpose, prerequisites, alternatives and exclusions for a 6-parameter tool. Nothing an agent needs to invoke 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 flight_number, origin, destination, depart_date and the cabin enum are already fully documented inline, including fallbacks like find_places. The description only restates 'needs the flight number, route and date', adding no syntax or constraint beyond the schema; 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?

States a specific verb and resource with scope: see which seats are open right now on one flight, and it enumerates the returned detail (seat numbers by row, window/aisle/middle/exit counts, pairs). It distinguishes itself from siblings by naming track_seats and explicitly excluding prices.

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 routing: use this for current availability, then use track_seats to be notified when a seat opens, and 'Not for prices' rules out price_calendar. The condition that selects each alternative is stated rather than implied.

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?