CheapCarRent search

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, priced in EUR, with pick-up and return at 12:00. 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

Name	Required	Description	Default
`city`	No
`iata`	No
`limit`	No
`offset`	No
`pickup`	No
`country`	No
`currency`	No
`driver_age`	No
`pickup_date`	Yes
`pickup_time`	No
`return_date`	Yes
`return_time`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A4.9/5.0

Behavior5/5

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

The description details critical behavioral aspects like the fixed 12:00 pickup/return times, the 17% online booking fee, and the payment structure (rest paid at pick-up). This goes far beyond the basic structure provided by annotations.

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 definition is highly detailed and slightly verbose, but every piece of information is crucial for correct execution or expectation setting. It is as concise as possible while providing all necessary operational context.

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 the high parameter count and lack of an output schema, this description is exceptionally complete. It covers constraints, data source limitations, pricing, and location parsing rules, providing the agent with full context to use the tool successfully.

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?

Since schema description coverage is 0%, the description must explain complex input semantics. It successfully clarifies the 'one location only' constraint and specifies the three accepted formats for location (pickup, country+city, or iata).

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 uses clear action verbs and precisely defines the resource being searched: 'current CheapCarRent car rental offers.' This clearly distinguishes its function from a general car rental search.

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

Usage Guidelines5/5

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

It provides extensive usage guidance, including hard operational limits such as the 30-day rental maximum and 365-day pickup window. It also sets realistic expectations by noting the result is 'not the whole market' and is not a guaranteed quote.

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

All CheapCarRent search tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?