lastminutedeals-api
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| X-API-Key | No | Free API key required for booking operations (search works without one). Obtain via POST to https://api.lastminutedealshq.com/api/keys/register. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_slotsA | |
| book_slotA | |
| get_booking_statusA | |
| get_supplier_infoA | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| find_experiences | Search for last-minute tours and activities in a specific destination. Args: city: City or country to search (e.g. "Reykjavik", "Rome", "Egypt"). hours_ahead: How soon the slot must start — in hours (default: 72). |
| explore_destinations | See all available destinations and experience types before searching. Use this to understand what's available across the supplier network. |
| autonomous_booking | Book a last-minute slot using a pre-funded agent wallet — no checkout required. Args: wallet_id: Pre-funded wallet ID (format: wlt_...). city: Optional city/destination to filter by. category: Optional category filter (e.g. 'experiences', 'wellness'). |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool serves a clearly distinct stage of the booking workflow: supplier discovery, slot search, booking creation, and status lookup. There is no meaningful overlap or ambiguity between them.
All tool names follow a consistent verb_noun snake_case pattern: get_booking_status, get_supplier_info, search_slots, book_slot. The naming is predictable and makes each tool's purpose immediately obvious.
Four tools is well-scoped for a last-minute deals booking API: it covers the essential user journey without unnecessary duplication. The count fits comfortably within the ideal 3–15 range.
The core lifecycle is covered: search supplier info, search slots, book, and check booking status. However, there is no cancel or list-bookings operation, and the status enum includes cancelled without providing a way to trigger it, leaving a minor lifecycle gap.