MCP server for hotel booking operations built with Spring Boot and Spring AI, exposing hotel search, booking, and management tools
Four tools with clear verb-noun naming (search_hotels, book_hotel, get_hotel_booking_by_reference, cancel_hotel_booking) and concise descriptions (40-60 chars). All tools have input schemas with typed parameters and descriptions. However, output schemas are not documented in the source code provided, and parameter descriptions lack format constraints (e.g., date format validation, email format). No error handling guidance visible. Risk annotations (READ_ONLY, WRITE, REVERSIBLE) are present but not reflected in tool annotations per MCP spec. Missing idempotency and confirmation patterns for destructive operations (book_hotel, cancel_hotel_booking).
Book a hotel for the given hotelId, check-in date, check-out date, guest name, and guest email
Cancel a hotel booking by booking reference
Get hotel booking details by booking reference
Search hotels in a city for the given check-in date, check-out date
Output schemas not documented. LLMs cannot plan downstream calls or extract required fields (e.g., hotelId from search_hotels result needed for book_hotel).
Parameter descriptions lack format constraints. 'Check-in date in ISO format (YYYY-MM-DD)' is stated but not enforced via schema pattern or validation. Email parameter has no format validation hint.
Destructive operations (book_hotel, cancel_hotel_booking) lack confirmation or dry-run patterns. Agents cannot preview consequences before executing irreversible bookings.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 62 | 2026-07-28+ | v2 |
No error handling guidance visible in source. Tools should return actionable error messages (e.g., 'Hotel not found. Try search_hotels() first') rather than raw exceptions.
Tool annotations (readOnlyHint, destructiveHint, idempotentHint) not visible in schema. Risk metadata (READ_ONLY, WRITE, REVERSIBLE) exists but not exposed via MCP tool annotations.