Skip to main content
Glama

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_car_rental_links"
  }
}

Input 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

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / lang / enum
      Previous value: -[
      -  "en",
      -  "de",
      -  "fr",
      -  "es",
      -  "it",
      -  "pl",
      -  "cs",
      -  "ja",
      -  "nl",
      -  "pt",
      -  "zh"
      -]New value: +[
      +  "en",
      +  "de",
      +  "fr",
      +  "es",
      +  "it",
      +  "pl",
      +  "ja",
      +  "nl",
      +  "pt",
      +  "zh"
      +]
  2. Changed10 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"Optional ISO 3166-1 alpha-2 country of the traveler; defaults to the caller's geolocation"New value: +"ISO 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."
    • addedInput schema / properties / country / pattern
      Added value: +"^[A-Za-z]{2}$"
    • changedInput schema / properties / destination / description
      Previous value: -"Country, island or city where the car is picked up, e.g. Iceland, Crete, Lisbon"New value: +"Country, island or city where the car is picked up, e.g. Iceland, Crete, Lisbon."
    • addedInput schema / properties / destination / maxLength
      Added value: +120
    • changedInput schema / properties / dropoff_date / description
      Previous value: -"Optional drop-off date, YYYY-MM-DD"New value: +"Drop-off date, YYYY-MM-DD. Echoed in the response; entered on the provider site."
    • addedInput schema / properties / dropoff_date / pattern
      Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
    • changedInput schema / properties / lang / description
      Previous value: -"Content language for the guides that come back (default \"en\")"New value: +"Language of the VoyageHacks guides returned. One of: en, de, fr, es, it, pl, cs, ja, nl, pt, zh. Defaults to \"en\"."
    • changedInput schema / properties / pickup_date / description
      Previous value: -"Optional pickup date, YYYY-MM-DD"New value: +"Pickup date, YYYY-MM-DD. Echoed in the response; entered on the provider site."
    • addedInput schema / properties / pickup_date / pattern
      Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "bookingCars": {
      +      "type": "string"
      +    },
      +    "destination": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "disclosure": {
      +      "type": "string"
      +    },
      +    "dropoff": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "guides": {
      +      "description": "Matching VoyageHacks guides that can be cited as sources.",
      +      "items": {
      +        "properties": {
      +          "section": {
      +            "type": "string"
      +          },
      +          "title": {
      +            "type": "string"
      +          },
      +          "url": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "title",
      +          "url"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "pickup": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "providers": {
      +      "items": {
      +        "properties": {
      +          "label": {
      +            "type": "string"
      +          },
      +          "url": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "label",
      +          "url"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "region": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "disclosure",
      +    "providers",
      +    "guides"
      +  ],
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnly/idempotent/openWorld/non-destructive) by disclosing that these are comparison landing pages with no live quotes, no availability and no reservation, that dates are echoed rather than embedded, and that links are affiliate links requiring disclosure. These are exactly the behavioral caveats an agent needs but cannot infer from structured fields.

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?

Front-loaded with the return value and provider list, then usage, then caveats. Every sentence carries information (providers, triggers, echo behavior, no-quotes disclaimer, affiliate disclosure), though the provider enumeration is dense and slightly prose-heavy.

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?

An output schema exists so return values needn't be described; the description still covers scope, trigger conditions, provider coverage, no-live-quote limitations and affiliate obligations. Nothing an agent needs to call and present results correctly is missing.

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 100%, so baseline is 3, but the description adds genuinely new semantics: pickup_date and dropoff_date are echoed for context rather than used to build the links. It does not clarify lang/country interaction beyond what the schema already says, so it is not a 5.

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?

States a specific verb and resource ('Return car and scooter rental comparison links for a destination') and enumerates the exact providers returned, so an agent can distinguish it from get_flight_links, get_hotel_links, or get_airport_transfer_links without opening a schema.

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?

Gives concrete triggering situations ('renting a car, a road trip, driving abroad, or an island or countryside trip that needs a vehicle'), which is clear when-to-use context. It stops short of naming an alternative tool or stating when NOT to call it, so it falls short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.