Skip to main content
Glama

get_booking_link

Read-only

Obtain a booking link for a hotel using dates and guest count. Supports deep-linking to a specific rate for direct checkout.

Instructions

Get booking options for a hotel.

Presents two explicit booking paths so the path is settled up front rather
than discovered mid-conversation:

1. **Check out on Gondola** with a booking link — always available.
2. **Book here now** with an eligible saved card — shown only when the user
   has a card that can be charged in chat, and referenced by its last 4.

Anonymous users get path 1 plus a prompt to sign up for in-chat booking.

Use this after search_hotels or get_hotel_details when a user wants to book.
Pass ``gondola_rate_id`` whenever a specific rate has been surfaced (from
get_hotel_details or compare_rates) so the link lands on that rate's
checkout page instead of the generic hotel page.

Args:
    hotel_id: The hotel's Vervotech property ID (from search_hotels results).
    checkin: Check-in date in YYYY-MM-DD format.
    checkout: Check-out date in YYYY-MM-DD format.
    num_adults: Number of adult guests. Defaults to 2.
    children_ages: Comma-separated ages of children (e.g. "5,8"). Empty string if no children.
    gondola_rate_id: Optional rate ID from get_hotel_details/compare_rates. When provided,
        the link deep-links straight to that rate's checkout page.

Returns:
    Booking instructions tailored to the user's auth status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
checkinYes
checkoutYes
hotel_idYes
num_adultsNo
children_agesNo
gondola_rate_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already mark it as read-only (readOnlyHint: true). The description adds context: anonymous users get only one path, card-eligible users get a second path, and deep-linking behavior. No contradictions with annotations.

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?

Well-structured with front-loaded purpose, clear bullet points for paths, and an Args section. Slightly lengthy but every sentence adds value. No fluff.

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 presence of an output schema (which likely documents return structure), the description covers all necessary aspects: purpose, usage context, parameter details, and auth-related behavior. Complete for the tool's complexity.

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?

Despite 0% schema description coverage, the description provides detailed parameter explanations in an Args section, including formats, defaults, and context (e.g., hotel_id from search_hotels, gondola_rate_id from get_hotel_details). Completely compensates for missing schema documentation.

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 it 'Get booking options for a hotel' and distinguishes two booking paths. It differentiates from sibling tools like book_hotel by focusing on presenting links/instructions rather than executing a booking, and specifies usage after search_hotels or get_hotel_details.

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 explicitly says to use after search_hotels or get_hotel_details when a user wants to book, and advises passing gondola_rate_id for deep-linking. It implies not to use for actual booking (reserved for book_hotel) but could be more direct about when not to use or alternatives.

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/gondola-ai/gondola-mcp'

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