Skip to main content
Glama
gondola-ai

Gondola AI

by gondola-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

get_vehicle_details

Read-only

Get full rental car details for a selected vehicle option, including extras, insurance options, charges, and cancellation policy.

Instructions

Get detailed information about a specific rental vehicle option.

Use this after search_vehicles to get extras, insurance options, charges, and cancellation policy.

Args:
    vendor_code: Vendor code from search results (e.g. "ZE" for Hertz, "AL" for Alamo).
    rate_code: Rate code from search results.
    search_id: Search ID from the vehicle search results.
    acriss_code: ACRISS code from the selected vehicle result.
    pickup_location: Pickup location from the selected vehicle result.
    vendor_location_id: Vendor desk identifier from the selected vehicle result.
    desk_kind: Desk classification from the selected vehicle result.

Returns:
    Vehicle details including extras, charges, and policies.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
desk_kindNo
rate_codeYes
search_idYes
acriss_codeNo
vendor_codeYes
pickup_locationNo
vendor_location_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.6
    • 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"
+}
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already mark this as read-only and non-destructive; the description adds the behavioral context that this is a follow-up lookup returning a specific set of detail categories such as extras, charges, and policies. No contradiction with the annotations.

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 front-loaded with the core purpose, then a one-line usage directive, then a clean parameter list and returns summary. No filler or redundant repetition of schema titles.

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 7-parameter lookup with an output schema, the description gives the prerequisite workflow, all parameter semantics, and the category of returned data. Nothing essential is missing for an agent to call it correctly.

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?

Schema coverage is 0%, but the description compensates fully by explaining every parameter's source and, for vendor_code, gives concrete examples ('ZE' for Hertz, 'AL' for Alamo). All seven parameters are accounted for in plain language.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action ('Get detailed information') on a specific resource ('specific rental vehicle option') and lists what is included: extras, insurance options, charges, and cancellation policy. It does not explicitly differentiate from the sibling get_vehicle_booking, which could overlap, so it falls just short of full sibling distinction.

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 to use it after search_vehicles, which sets clear context and ordering. It does not name alternatives or exclusions, so it gets a 4 rather than a 5.

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

Deploy Server

Other Tools