OlaChill Japan Travel

Find a car with driver by day or hour

search_chauffeur_services

Read-onlyIdempotent

Use this when the user wants a private car with a driver in Japan by the day or by the hour, for example a chauffeured Toyota Alphard, Lexus LM, Lexus LS, Lexus LX, Lexus ES, Toyota Crown or Mercedes V-Class for city sightseeing, business meetings, shopping or a day trip with a driver who waits. Returns each vehicle with passenger and suitcase capacity, the day-hire price per car for the chosen prefecture or the hourly reference rate for Tokyo, whether the price is confirmed or a class-tier estimate, and how booking and payment work. Read-only. Do not use it for a one-way ride between an airport and a city or resort (use search_private_transfers), for more than six passengers or for buses and coaches (use search_charter_vehicles), for self-drive car rental (use list_olachill_services), or for taxis.

Input Schema

TableJSON Schema

Name	Required	Description
`date`	No	Pickup date as YYYY-MM-DD (Japan time). Used to apply the short-notice surcharge to the day-hire total.
`days`	No	Daily hire only: number of hire days (1–7). Default 1.
`hours`	No	Hourly hire only: hours needed, 2 to 12 in half-hour steps. Default 2.
`locale`	No	Language for product names and page links (en, ja, ko, zh = Simplified Chinese, tw = Traditional Chinese, es, fr, de, it, th, id, vi). Default en.
`hire_type`	No	daily = flat price per car per day; hourly = hourly reference rate (Tokyo, quoted on request); any = both. Default any.
`large_bags`	No	Number of large suitcases carried in the car. Default 0.
`passengers`	No	Number of travellers in the car (children count as passengers).
`prefecture`	No	Japanese prefecture or major city of the pickup, in English, e.g. Tokyo, Osaka, Kyoto, Hokkaido, Kanagawa, Yokohama, Nagoya. Day-hire prices differ by prefecture. Omit for Tokyo prices.

Output Schema

TableJSON Schema

Name	Required	Description
`hint`	No	What to try next.
`error`	No	Present only when the call failed; a short reason the user can act on.
`results`	Yes
`prefecture`	No	Prefecture the day-hire prices were computed for.
`group_too_large`	No	True when no car fits the party and luggage; use search_charter_vehicles instead.
`earliest_bookable_date`	No	First pickup date (Japan time) that can be booked today.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 7, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the description's 'Read-only' restates that, which is redundant. It does add value beyond the structured fields by disclosing the pricing model (day-hire per car per prefecture vs hourly reference rate for Tokyo), the confirmed-vs-estimate distinction, and that booking/payment behavior is returned.

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 core capability and the exclusion routing, both high-value. It runs long and the long enumeration of vehicle models (Alphard, LM, LS, LX, ES, Crown, V-Class) is illustrative padding, but every other clause earns its place.

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 the description needn't detail returns, yet it still summarizes them; annotations cover the safety profile; and all 8 parameters are fully documented in-schema. An agent has everything needed to select and call this correctly.

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 the baseline is 3. The description adds meaning on top by linking hire_type/prefecture to the pricing outcome (day-hire by prefecture, hourly Tokyo reference rate) and noting the waiting-driver model, which helps an agent pick parameters rather than merely echo the schema text.

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?

Specific verb+resource (find a private car with driver) with scope (by the day or by the hour in Japan) and concrete examples of vehicle classes and use cases. It explicitly distinguishes itself from search_private_transfers, search_charter_vehicles, list_olachill_services and taxis, so an agent can route correctly without opening any schema.

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?

Explicit when-to-use (day or hourly chauffeured car for sightseeing, business, shopping, day trip with waiting driver) and when-not-to-use with named alternatives for each exclusion (one-way airport transfers, >6 passengers, buses/coaches, self-drive, taxis). Nothing is left to inference.

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

All OlaChill Japan Travel 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?