Skip to main content
Glama

book_vehicle

Destructive

Book a rental vehicle from search results. Provide search ID, vendor, rate, vehicle code, renter details, and payment ID to confirm reservation.

Instructions

Book a rental vehicle from a search result.

Requires a Gondola account (API key) and a saved payment method.
Use get_payment_methods to find your payment ID.

Args:
    search_id: Search ID from search_vehicles.
    vendor_code: Vendor code from search results (e.g. "ZE" for Hertz).
    rate_code: Rate code of the selected vehicle from search results.
    acriss_code: ACRISS vehicle classification code from search results.
    given_name: Renter's first name.
    family_name: Renter's last name.
    email_address: Renter's email for confirmation.
    phone_number: Renter's phone number with country code (e.g. "+1-555-123-4567").
    payment_id: Payment method ID from get_payment_methods.
    pickup_location: Optional pickup IATA code for the selected vehicle (disambiguates metro fanouts).
    loyalty_account_id: Optional loyalty account ID to earn points on this rental.

Returns:
    Booking confirmation with ID and details, or an error message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rate_codeYes
search_idYes
given_nameYes
payment_idYes
acriss_codeYes
family_nameYes
vendor_codeYes
phone_numberYes
email_addressYes
pickup_locationNo
loyalty_account_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. Description adds that it requires an account and payment, but could further disclose potential charges or irreversibility. No contradiction with 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 concise with clear sections (prerequisites, args, returns). Every sentence adds value with 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 11 parameters, 9 required, and an output schema, the description covers prerequisites, parameter details, and returns adequately for invocation.

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?

With 0% schema coverage, the description fully explains all 11 parameters, including sources (e.g., 'from search results'), format (e.g., phone number example), and optional usage (disambiguation, loyalty points).

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 'Book a rental vehicle from a search result.' with a specific verb and resource, distinguishing it from sibling tools like search_vehicles and cancel_vehicle_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?

Prerequisites are explicitly listed (requires Gondola account and saved payment method) and refers to get_payment_methods for the payment ID. It explains where to obtain search_id, vendor_code, etc. No explicit when-not usage, but context is clear.

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