Skip to main content
Glama

search_slots

Find last-minute available tours and activities from multiple suppliers, sorted by urgency to help you book time-sensitive travel experiences.

Instructions

Search for last-minute available tours and activities.

Returns real production inventory from 19 suppliers (Adi Tours - Nuba travel, All Washington View,
Arctic Adventures, Bicycle Roma, Boka Bliss, EgyExcursions, Hillborn Experiences,
Íshestar Riding Tours, Marvel Egypt Tours, O Turista Tours, Pure Morocco Experience,
REDRIB Experience, Ramen Factory Kyoto, TourTransfer Bucharest, Tours El Chiquiz,
Trivanzo Holidays, TUTU VIEW Ltd, Vakare Travel Service, Zestro Bizlinks) sourced live via the OCTO open booking protocol.
Slots are sorted by urgency (soonest first).

Args:
    city:        City or country filter, partial match (e.g. "Reykjavik", "Rome", "Iceland").
                 Leave empty to search all locations.
    category:    Category filter. Use "experiences" for tours/activities.
                 Leave empty for all categories.
    hours_ahead: Return slots starting within this many hours (default: 72).
    max_price:   Maximum price in USD. Set to 0 to return all prices.
    limit:       Max results to return (default 50). Results are sorted by urgency
                 so the most time-sensitive slots come first. Increase for broader
                 browsing (e.g. limit=500). Use city/category filters to narrow
                 results instead of raising the limit when possible.

Returns:
    List of available slot dicts sorted by hours_until_start (soonest first).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNo
categoryNo
hours_aheadNo
max_priceNo
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: it returns 'real production inventory' from 19 specific suppliers, uses 'live' sourcing via OCTO protocol, sorts by urgency (soonest first), and explains result sorting logic. It doesn't mention rate limits or authentication requirements, but provides substantial operational context.

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?

The description is efficiently structured with purpose statement, supplier list, sorting explanation, parameter documentation, and return format - all in appropriate detail. Every sentence adds value, and it's well-organized with clear sections for Args and Returns.

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?

Given the tool's complexity (5 parameters, no annotations, but has output schema), the description is remarkably complete. It covers purpose, behavioral context, detailed parameter semantics, and explains the return format. With an output schema present, it appropriately doesn't need to detail return value structure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates by providing detailed semantics for all 5 parameters: explains city accepts partial matches and can be empty, specifies category should be 'experiences' for tours/activities, clarifies hours_ahead default and meaning, explains max_price=0 means all prices, and provides nuanced guidance on limit usage with sorting implications.

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?

The description clearly states the tool searches for 'last-minute available tours and activities' with specific details about real inventory from 19 suppliers via OCTO protocol. It distinguishes from siblings like book_slot (booking) and get_booking_status (status checking) by focusing on search functionality.

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?

The description provides clear context for when to use this tool (searching for last-minute tours/activities) and includes practical guidance like 'Use city/category filters to narrow results instead of raising the limit when possible.' However, it doesn't explicitly state when NOT to use it or mention alternatives among sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/johnanleitner1-Coder/lastminutedeals-api'

If you have feedback or need assistance with the MCP directory API, please join our Discord server