Skip to main content
Glama

VoyageHacks

by com.voyagehacks

Get car and scooter rental links

get_car_rental_links
Read-onlyIdempotent

Return car and scooter rental comparison links for a destination: EconomyBookings and QEEQ for worldwide comparison, Localrent and GetRentacar for local suppliers with lower deposits in southern Europe, Georgia, the Balkans and Asia, BikesBooking for scooters and motorbikes, and Booking.com Cars, plus up to four VoyageHacks car-rental guides for that country covering real prices, insurance excess and one-way fees. Useful when a user mentions renting a car, a road trip, driving abroad, or an island or countryside trip that needs a vehicle. These are comparison landing pages: dates and the pickup point are entered on the provider site, so pickup_date and dropoff_date are echoed in the response for context rather than embedded in the links. No live quotes, no vehicle availability and no reservation. Affiliate links: VoyageHacks may earn a commission at no additional cost to the traveler, which should be disclosed when the links are presented.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoLanguage of the VoyageHacks guides returned. One of: en, de, fr, es, it, pl, cs, ja, nl, pt, zh. Defaults to "en".
countryNoISO 3166-1 alpha-2 country the traveler is booking from, e.g. US, DE, GB. Selects the regional Booking.com programme. Defaults to the caller's geolocation, then to the language default.
destinationNoCountry, island or city where the car is picked up, e.g. Iceland, Crete, Lisbon.
pickup_dateNoPickup date, YYYY-MM-DD. Echoed in the response; entered on the provider site.
dropoff_dateNoDrop-off date, YYYY-MM-DD. Echoed in the response; entered on the provider site.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
guidesYesMatching VoyageHacks guides that can be cited as sources.
pickupNo
regionNo
dropoffNo
providersYes
disclosureYes
bookingCarsNo
destinationNo

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint false), the description explains that these are comparison landing pages, that dates are echoed for context rather than embedded in links, and that there are 'no live quotes, no vehicle availability and no reservation.' It also discloses affiliate commissions, which is important operational context.

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 four sentences, each carrying distinct information: returned items, expected use cases, behavioral caveats, and affiliate disclosure. It is front-loaded and contains no filler or repetition of schema content.

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?

With an output schema present, an agent does not need the description to explain return values. The description covers provider scope, regional variants, use-case triggers, link behavior, and disclosure requirements, making the tool fully understandable for safe 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 coverage is 100%, so the baseline is 3. The description adds semantic value by explaining that pickup_date and dropoff_date are echoed for context rather than used in the generated links, and that country selects the regional Booking.com programme, details not present in the 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?

The description states a specific verb and resource: 'Return car and scooter rental comparison links for a destination', then names providers and guides. It clearly differentiates this tool from siblings like get_hotel_links and get_flight_links without relying on the title alone.

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 explicit trigger conditions: 'Useful when a user mentions renring a car, a road trip, driving abroad, or an island or countryside trip that needs a vehicle.' It does not mention sibling alternatives by name or state when-not-to-use conditions, but the use cases are clear enough for basic routing.

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

All VoyageHacks toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation4/5

The tools split into clear families: category-specific link builders, a whole-trip aggregate link builder, article search/fetch, and gear search/recommendation. The only mild overlap is between get_booking_links and the individual category link tools, but their aggregate-vs-category purpose is explicitly described, so an agent should rarely misselect.

Naming Consistency5/5

Nearly all tools follow the verb_noun snake_case pattern, led by the get_<category>_links family, with search_articles and search_travel_gear matching the same convention. There is no camelCase, no mixed verb styles, and the pattern is highly predictable from the tool names alone.

Tool Count5/5

Twelve tools is well-scoped for a travel planning and affiliate-link server: seven category link builders, one aggregate trip link builder, two article tools, and two travel gear tools. Each tool covers a distinct part of the workflow and none feels redundant or like padding.

Completeness4/5

The travel-planning surface is largely complete: research, flights, hotels, airport transfers, car rental, eSIM, VPN, credit cards, and gear are all covered, with an aggregate tool for whole-trip planning. Minor gaps, such as no dedicated train or attractions/tours link builder, keep it from a perfect score.

Resources