MCP server for airline ticketing operations. Exposes three tools over stdio transport: query_flights, buy_ticket, and check_in. Routes all HTTP calls through an Ocelot gateway to interact with SE4458 Airline Ticketing APIs.
Three tools with complete input schemas and descriptions, but descriptions are verbose (200+ chars) and lack LLM-optimized structure. Parameter descriptions are present but generic. No output schemas documented. Error handling returns raw HTTP status codes without recovery guidance. Tools follow verb_noun naming but descriptions bury key details in prose rather than stating WHAT/WHEN/WHY upfront. No tool annotations (readOnlyHint/destructiveHint) despite buy_ticket and check_in being destructive operations.
Book/purchase a flight ticket for one or more passengers. Requires flight number, departure datetime (YYYY-MM-DDTHH:MM:SS), and the full names of every passenger. Authenticates automatically with constant credentials before hitting the gateway.
Check in a passenger for an existing booking. Requires the flight number, the scheduled departure datetime (YYYY-MM-DDTHH:MM:SS), and the passenger's full name.
Search for available flights between two airports. The user may provide city names (e.g. Istanbul, Frankfurt) or airport codes (e.g. IST, FRA). Dates must be in ISO format (YYYY-MM-DD); use the same value for departure_date_from and departure_date_to for a single-day search. Returns the raw JSON response from the gateway as a string.
Destructive operations (buy_ticket, check_in) lack tool annotations. Missing readOnlyHint=false and destructiveHint=true prevents LLMs from recognizing irreversible side effects and planning accordingly.
Error responses return raw HTTP status codes and gateway text without recovery guidance. 'Flight query failed with status 400: ...' tells LLM nothing about what to fix. Should return 'Invalid airport code. Try search_airports() or use IATA codes (e.g., IST, FRA).'
No output schema documented. LLMs cannot plan downstream operations or extract required fields. buy_ticket and check_in responses are raw JSON strings, should document structure (booking_id, confirmation_number, status fields).
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 57 | 2026-07-28+ | v2 |
Descriptions exceed 200 chars and bury key details in prose. 'Search for available flights between two airports. The user may provide...' should lead with action: 'Search flights by origin/destination and date range. Accepts city names or IATA codes. Returns paginated results.'
query_flights returns raw JSON string, not structured object. LLM must parse unstructured text to extract flight details, increasing token waste and hallucination risk. Should return array of {flight_number, departure, arrival, price, seats_available}.