Skip to main content
Glama
gondola-ai

Gondola AI

by gondola-ai
OverviewSchemaRelated ServersScoreDiscussions
JavaScript

get_vehicle_details

Read-only

Retrieves rental vehicle details including extras, insurance options, charges, and cancellation policy for a specific vehicle option.

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.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rate_codeYes
search_idYes
vendor_codeYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, destructiveHint. Description adds value by specifying the type of details returned, without contradicting 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?

Description is extremely concise, with clear sections for purpose, usage, and arguments. Every sentence adds value, no redundancy.

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 simple retrieval nature, output schema exists, and description covers usage, parameters, and expected details. Complete for agent decision-making.

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 explains all three parameters with examples ('ZE' for Hertz, 'AL' for Alamo) and links them to search results. Fully compensates for missing schema 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?

Description clearly states it gets detailed information about a rental vehicle option, listing specific details (extras, insurance, charges, cancellation policy). Purpose is distinct from sibling tools like search_vehicles or book_vehicle.

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?

Explicitly says 'Use this after search_vehicles', providing clear context and sequence. Does not mention when not to use, but the guidance is sufficient.

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