Skip to main content
Glama

Gondola Award Travel Search

by ai.gondola
OverviewDiscussionsAdmin

get_booking_link

Read-only

Get a booking link for a hotel on Gondola. Use this when a user wants to book a specific hotel. Returns a URL to the hotel's booking page with dates pre-filled. Pass gondola_rate_id when a specific rate is known so the link deep-links straight to that rate's checkout page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
checkinYesCheck-in date in YYYY-MM-DD format.
checkoutYesCheck-out date in YYYY-MM-DD format.
hotel_idYesThe hotel's Vervotech property ID.
num_adultsNoNumber of adult guests.
gondola_rate_idNoOptional rate ID from get_hotel_rates or compare_rates. When provided, the link deep-links straight to that rate's checkout page instead of the generic hotel page.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / gondola_rate_id / description
      Previous value: -"Optional rate ID from get_hotel_details or compare_rates. When provided, the link deep-links straight to that rate's checkout page instead of the generic hotel page."New value: +"Optional rate ID from get_hotel_rates or compare_rates. When provided, the link deep-links straight to that rate's checkout page instead of the generic hotel page."
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "get_booking_linkOutput",
+  "type": "object"
+}
  3. Changed16 schema fields changed
    • addedInput schema / properties / checkin / description
      Added value: +"Check-in date in YYYY-MM-DD format."
    • removedInput schema / properties / checkin / title
      Removed value: -"Checkin"
    • addedInput schema / properties / checkout / description
      Added value: +"Check-out date in YYYY-MM-DD format."
    • removedInput schema / properties / checkout / title
      Removed value: -"Checkout"
    • removedInput schema / properties / children_ages
      Removed value: -{
-  "default": "",
-  "title": "Children Ages",
-  "type": "string"
-}
    • removedInput schema / properties / gondola_rate_id / anyOf
      Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / gondola_rate_id / default
      Removed value: -null
    • addedInput schema / properties / gondola_rate_id / description
      Added value: +"Optional rate ID from get_hotel_details or compare_rates. When provided, the link deep-links straight to that rate's checkout page instead of the generic hotel page."
    • removedInput schema / properties / gondola_rate_id / title
      Removed value: -"Gondola Rate Id"
    • addedInput schema / properties / gondola_rate_id / type
      Added value: +"integer"
    • addedInput schema / properties / hotel_id / description
      Added value: +"The hotel's Vervotech property ID."
    • removedInput schema / properties / hotel_id / title
      Removed value: -"Hotel Id"
    • addedInput schema / properties / num_adults / description
      Added value: +"Number of adult guests."
    • removedInput schema / properties / num_adults / title
      Removed value: -"Num Adults"
    • removedInput schema / title
      Removed value: -"get_booking_linkArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_booking_linkOutput",
-  "type": "object"
-}New value: +null
  4. Changed1 schema field changed
    • addedInput schema / properties / gondola_rate_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Gondola Rate Id"
+}
  5. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds behavioral detail beyond annotations: it returns a URL, pre-fills dates, and changes link destination when gondola_rate_id is present. No contradiction with annotations is present.

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?

Three sentences, front-loaded with the main purpose, followed by usage context and optional-parameter behavior. Every sentence contributes meaningful guidance, with no repetition of schema details or filler.

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?

The description covers purpose, when to use it, what it returns, and how the optional parameter changes behavior. With an output schema present and annotations covering the read-only nature, the description is complete for an agent to select and invoke this tool correctly.

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

Parameters4/5

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

Schema coverage is 100%, so parameters are already well-documented in the schema. The description adds value by clarifying the effect of gondola_rate_id (deep-linking to that rate's checkout page) and the pre-filled dates behavior, which enriches the schema's basic parameter descriptions.

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 a specific verb ('Get'), a resource ('a booking link for a hotel on Gondola'), and the core behavior (returns a URL with dates pre-filled). It distinguishes itself from sibling tools like book_hotel and get_vehicle_booking_link by specifying 'hotel' and the return of a URL rather than performing a booking.

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?

It explicitly says 'Use this when a user wants to book a specific hotel,' giving a clear context. It also provides conditional guidance for the optional gondola_rate_id to deep-link to a rate's checkout page. However, it does not explicitly contrast itself with book_hotel or other booking-related siblings, so some inference is left to the agent.

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

All Gondola Award Travel Search toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources