Skip to main content
Glama
gondola-ai

Gondola AI

by gondola-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

get_vehicle_booking_link

Read-only

Generate a direct booking link for a chosen vehicle from search results, so travelers can review the rate and finalize the reservation on the checkout page.

Instructions

Get a Gondola.ai deep link for a specific vehicle from search results.

Returns a link to Gondola's checkout for this vehicle, where the traveler reviews the rate
and completes the reservation on the web. This is the booking path for this connection.

(Connections belonging to an approved booking partner — which requires the mcp:book OAuth
scope — additionally get an in-conversation option here.)

Args:
    search_id: Search ID from search_vehicles.
    vendor_code: Vendor code from search results.
    rate_code: Rate code of the selected vehicle.
    pickup_datetime: Pickup date and time in ISO format.
    dropoff_datetime: Drop-off date and time in ISO format.

Returns:
    Booking instructions tailored to the user's auth status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rate_codeYes
search_idYes
vendor_codeYes
pickup_datetimeYes
dropoff_datetimeYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 adds meaningful behavioral context: it returns a checkout link, requires the mcp:book OAuth scope for partner-specific in-conversation options, and returns booking instructions tailored to the user's auth status. No contradiction with annotations is present.

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?

The description is well-structured with a concise main statement followed by an Args/Returns breakdown. The parenthetical about partner OAuth scope is relevant and not filler, though the Returns line is slightly vague and could be more explicit.

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 retrieval tool with 5 required parameters and an output schema, the description provides enough information to invoke the tool correctly. It identifies the source of each parameter, notes auth-dependent behavior, and clarifies the booking flow. Minor gaps like exact datetime format variants or error behavior are not critical for selection and invocation.

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

Parameters4/5

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

Schema description coverage is 0%, so the description carries the burden of documenting all 5 parameters. It names each argument and adds source context ('from search_vehicles', 'from search results') and format guidance for datetimes ('ISO format'), which goes beyond the bare schema property titles.

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 clearly states the tool gets a Gondola.ai deep link for a specific vehicle from search results, which is a specific verb-resource pairing. It does not explicitly name sibling tools like get_vehicle_booking or get_booking_link, but the phrase 'deep link' and 'checkout' makes the function reasonably distinct.

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

Usage Guidelines3/5

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

The description provides useful context: it is the booking path for a connection and may return an in-conversation option for approved booking partners with the mcp:book OAuth scope. However, it does not explicitly say when to prefer this tool over alternatives such as get_vehicle_booking or get_booking_link, leaving some routing to inference.

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