Skip to main content
Glama

Search cars

search_cars
Read-onlyIdempotent

Search current CheapCarRent car rental offers for one place and dates. This is the same city preview as the website, with pick-up and return at 12:00. Each offer has its price in its own currency and priceEur, the same day price in EUR; offers are sorted by priceEur, cheapest first. A rental can run up to 30 days, and pick-up must be within 365 days. The result is one page of at most 8 offers, not the whole market. An empty page is a normal result, not a failure. Prices are not a guaranteed quote. Use each offer URL on https://cheapcarent.com for the live price and that offer's terms. The online booking fee is 17%. The rest of the rental is paid at pick-up. Pass one location only: pickup, or country plus city, or iata.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pickup_date": "<pickup_date>",
      "return_date": "<return_date>"
    },
    "name": "search_cars"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNocityParam from list_locations, e.g. barcelona. Pass together with country.
iataNoThree-letter airport code from list_locations, e.g. BCN. Use instead of country + city.
limitNoHow many offers to return, 1 to 8. Default 8.
offsetNoHow many of the cheapest offers to skip, for the next page. Default 0.
pickupNoFree-text place name, e.g. Barcelona. Use only when list_locations gave no exact match; prefer country + city or iata.
countryNocountryCode from list_locations, e.g. ES. Pass together with city.
currencyNoOnly EUR is accepted. Offers keep their own currency in price; priceEur is always in EUR.
driver_ageNoDriver's age in years, 18 to 99. Accepted but not used for prices: the preview is priced for a standard adult driver; age terms are on each offer's page.
pickup_dateYesPick-up date, YYYY-MM-DD. Today or later, within 365 days.
pickup_timeNoPick-up time. Only 12:00 is supported; may be left out.
return_dateYesReturn date, YYYY-MM-DD. 1 to 30 days after pickup_date.
return_timeNoReturn time. Only 12:00 is supported; may be left out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • addedInput schema / properties / city / description
      Added value: +"cityParam from list_locations, e.g. barcelona. Pass together with country."
    • addedInput schema / properties / country / description
      Added value: +"countryCode from list_locations, e.g. ES. Pass together with city."
    • addedInput schema / properties / currency / description
      Added value: +"Only EUR is accepted. Offers keep their own currency in price; priceEur is always in EUR."
    • addedInput schema / properties / driver_age / description
      Added value: +"Driver's age in years, 18 to 99. Accepted but not used for prices: the preview is priced for a standard adult driver; age terms are on each offer's page."
    • addedInput schema / properties / iata / description
      Added value: +"Three-letter airport code from list_locations, e.g. BCN. Use instead of country + city."
    • addedInput schema / properties / limit / description
      Added value: +"How many offers to return, 1 to 8. Default 8."
    • addedInput schema / properties / offset / description
      Added value: +"How many of the cheapest offers to skip, for the next page. Default 0."
    • addedInput schema / properties / pickup / description
      Added value: +"Free-text place name, e.g. Barcelona. Use only when list_locations gave no exact match; prefer country + city or iata."
    • addedInput schema / properties / pickup_date / description
      Added value: +"Pick-up date, YYYY-MM-DD. Today or later, within 365 days."
    • addedInput schema / properties / pickup_time / description
      Added value: +"Pick-up time. Only 12:00 is supported; may be left out."
    • addedInput schema / properties / return_date / description
      Added value: +"Return date, YYYY-MM-DD. 1 to 30 days after pickup_date."
    • addedInput schema / properties / return_time / description
      Added value: +"Return time. Only 12:00 is supported; may be left out."
  2. Changed1 schema field changed
    • changedInput schema / properties / limit / maximum
      Previous value: -20New value: +8
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, open-world behavior, yet the description adds substantial behavioral context: results are capped at 8 per page, sorting is by priceEur ascending, an empty page is a normal outcome, prices are not a guaranteed quote, the 17% booking fee is online-only with the balance due at pick-up, and rental duration is limited to 30 days within a 365-day booking window.

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?

Dense but front-loaded: purpose first, then result shape, then pricing caveats, then input rules. Every sentence carries information, though the single-paragraph block of caveats is slightly packed compared with the crisp opening line.

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 12 parameters and no output schema, the description still explains the return shape (one page, at most 8 offers, sorted cheapest first, per-offer currency plus priceEur) and the limits bounding each call. Nothing essential for a correct first invocation 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 coverage is 100% so parameter names and formats are already documented, but the description adds meaning the schema cannot express: location inputs are mutually exclusive (pick one form), and times are effectively fixed at 12:00. These constraints materially change how an agent fills the arguments.

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 (search) and resource (car rental offers) with explicit scope: one place, given dates, city-preview with fixed 12:00 pick-up/return. An agent can tell this apart from list_locations, which is only referenced for resolving location identifiers.

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 usage constraints: 'Pass one location only: pickup, or country plus city, or iata' and points to offer URLs for live pricing and terms. It stops short of an explicit when-not statement, but the location-input rule and the pointer to per-offer pages cover the main decision points.

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.

Resources