Gondola Award Travel Search

get_vehicle_booking_link

Read-only

Get a Gondola.ai deep link for a specific vehicle from search results. Use this to share a booking page URL the user can complete on the web, or as a fallback when in-conversation booking via book_vehicle is unavailable. Returns a Gondola checkout link for the selected vehicle; the traveler completes the reservation there. In-conversation booking via book_vehicle is partner-only.

Input Schema

TableJSON Schema

Name	Required	Description
`rate_code`	Yes	Rate code of the selected vehicle.
`search_id`	Yes	Search ID from search_vehicles.
`vendor_code`	Yes	Vendor code from search results.
`pickup_datetime`	Yes	Pickup date and time in ISO format (e.g. "2025-03-15T10:00:00").
`dropoff_datetime`	Yes	Drop-off date and time in ISO format (e.g. "2025-03-20T10:00:00").

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "get_vehicle_booking_linkOutput",
+  "type": "object"
+}

Changed12 schema fields changedAug 26, 2026

addedInput schema / properties / dropoff_datetime / description

Added value: +"Drop-off date and time in ISO format (e.g. \"2025-03-20T10:00:00\")."

removedInput schema / properties / dropoff_datetime / title
```
Removed value: -"Dropoff Datetime"
```

addedInput schema / properties / pickup_datetime / description

Added value: +"Pickup date and time in ISO format (e.g. \"2025-03-15T10:00:00\")."

removedInput schema / properties / pickup_datetime / title
```
Removed value: -"Pickup Datetime"
```
addedInput schema / properties / rate_code / description
```
Added value: +"Rate code of the selected vehicle."
```
removedInput schema / properties / rate_code / title
```
Removed value: -"Rate Code"
```
addedInput schema / properties / search_id / description
```
Added value: +"Search ID from search_vehicles."
```
removedInput schema / properties / search_id / title
```
Removed value: -"Search Id"
```
addedInput schema / properties / vendor_code / description
```
Added value: +"Vendor code from search results."
```
removedInput schema / properties / vendor_code / title
```
Removed value: -"Vendor Code"
```

removedInput schema / title

Removed value: -"get_vehicle_booking_linkArguments"

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_vehicle_booking_linkOutput",
-  "type": "object"
-}New value: +null

First observedJun 18, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already convey read-only and non-destructive behavior, so the description adds value by explaining that the traveler completes the reservation on the web and that in-conversation booking via book_vehicle is partner-only. This clarifies the operational outcome beyond the schema and 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?

Three sentences with no wasted content: purpose, usage, and return/fallback context are each covered. It is front-loaded and efficiently structured, though the first and third sentences overlap slightly in describing the return value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only link-generation tool with a full input schema and an output schema present, the description is nearly complete. It covers what the tool returns, when to use it, and the key fallback condition. Minor details like authentication or link expiration are not addressed, but they are not essential for correctness.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all five required parameters. The description adds general context by tying the parameters to search results but does not add parameter-level meaning beyond what the schema provides; the baseline of 3 is appropriate.

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?

Description states a specific verb and resource: getting a Gondola.ai deep link/checkout link for a specific vehicle from search results. It clearly distinguishes the tool from booking tools by emphasizing the returned artifact is a shareable web URL where the traveler completes the reservation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use it: to share a booking page URL for web completion, or as a fallback when in-conversation booking via book_vehicle is unavailable. It also names the alternative and the condition that selects it, which is strong usage guidance.

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 tools Inspect

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.