Gondola Award Travel Search

get_vehicle_details

Read-only

Get detailed information about a specific rental vehicle option. Use this after search_vehicles to get extras, insurance options, charges, and cancellation policy for the vehicle the user wants to book.

Input Schema

TableJSON Schema

Name	Required	Description
`desk_kind`	No	Desk classification from the selected vehicle result, when present.
`rate_code`	Yes	Rate code from search results.
`search_id`	Yes	Search ID from the vehicle search results.
`acriss_code`	No	ACRISS code from the selected vehicle result; pass it through to disambiguate classes.
`vendor_code`	Yes	Vendor code from search results (e.g. "ZE" for Hertz, "AL" for Alamo).
`pickup_location`	No	Pickup location from the selected vehicle result; pass it through for metro searches.
`vendor_location_id`	No	Vendor desk identifier from the selected vehicle result, when present.

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_detailsOutput",
+  "type": "object"
+}

Changed28 schema fields changedAug 26, 2026

removedInput schema / properties / acriss_code / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / acriss_code / default
```
Removed value: -null
```

addedInput schema / properties / acriss_code / description

Added value: +"ACRISS code from the selected vehicle result; pass it through to disambiguate classes."

removedInput schema / properties / acriss_code / title
```
Removed value: -"Acriss Code"
```
addedInput schema / properties / acriss_code / type
```
Added value: +"string"
```

removedInput schema / properties / desk_kind / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / desk_kind / default
```
Removed value: -null
```

addedInput schema / properties / desk_kind / description

Added value: +"Desk classification from the selected vehicle result, when present."

removedInput schema / properties / desk_kind / title
```
Removed value: -"Desk Kind"
```
addedInput schema / properties / desk_kind / type
```
Added value: +"string"
```

removedInput schema / properties / pickup_location / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / pickup_location / default
```
Removed value: -null
```

addedInput schema / properties / pickup_location / description

Added value: +"Pickup location from the selected vehicle result; pass it through for metro searches."

removedInput schema / properties / pickup_location / title
```
Removed value: -"Pickup Location"
```
addedInput schema / properties / pickup_location / type
```
Added value: +"string"
```
addedInput schema / properties / rate_code / description
```
Added value: +"Rate code from search results."
```
removedInput schema / properties / rate_code / title
```
Removed value: -"Rate Code"
```

addedInput schema / properties / search_id / description

Added value: +"Search ID from the vehicle search results."

removedInput schema / properties / search_id / title
```
Removed value: -"Search Id"
```

addedInput schema / properties / vendor_code / description

Added value: +"Vendor code from search results (e.g. \"ZE\" for Hertz, \"AL\" for Alamo)."

removedInput schema / properties / vendor_code / title
```
Removed value: -"Vendor Code"
```

removedInput schema / properties / vendor_location_id / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / vendor_location_id / default
```
Removed value: -null
```

addedInput schema / properties / vendor_location_id / description

Added value: +"Vendor desk identifier from the selected vehicle result, when present."

removedInput schema / properties / vendor_location_id / title
```
Removed value: -"Vendor Location Id"
```
addedInput schema / properties / vendor_location_id / type
```
Added value: +"string"
```

removedInput schema / title

Removed value: -"get_vehicle_detailsArguments"

changedOutput schema / (root)

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

Changed4 schema fields changedAug 14, 2026

addedInput schema / properties / acriss_code

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Acriss Code"
+}

addedInput schema / properties / desk_kind

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Desk Kind"
+}

addedInput schema / properties / pickup_location

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Pickup Location"
+}

addedInput schema / properties / vendor_location_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Vendor Location Id"
+}

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 declare readOnlyHint=true and destructiveHint=false, and the description aligns with that by saying 'Get detailed information.' It adds behavioral context beyond annotations by specifying what categories of details are returned. Since an output schema exists, the description does not need to enumerate return fields.

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 two sentences with no filler. The first sentence states the core function directly, and the second provides workflow context and the content categories the agent can expect. Every word earns its place.

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?

For a read-only detail tool with a full output schema, complete parameter documentation, and annotations covering safety, the description covers purpose, relationship to search_Vehicles, and the types of information returned. Nothing critical for selecting and invoking the tool is missing.

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 each parameter already has a clear definition such as 'Rate code from search results.' The description reinforces the workflow context by saying to use it after search_vehicles, but it does not add parameter-specific meaning beyond the schema. Baseline 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?

The description uses a specific verb ('Get') and a concrete resource ('detailed information about a specific rental vehicle option'). It also names the exact content areas (extras, insurance options, charges, cancellation policy) and positions the tool as the follow-up to search_vehicles, which distinguishes it from search and booking-focused siblings.

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 gives a clear trigger condition: 'Use this after search_vehicles to get extras, insurance options, charges, and cancellation policy for the vehicle the user wants to book.' It does not explicitly state when not to use it or name alternatives like get_vehicle_booking, but the workflow context is clear enough for an agent to route correctly.

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.