Every vehicle on the connected account, and which one the tools act on.

Use for: which cars can I ask about? Choosing one is toyota_select_vehicle.

Point every other tool at one vehicle of the account, and remember it.

Use when the account holds several vehicles, or to switch between them.

Model, year, plate, colour, first-use date, connected-services subscriptions and which remote capabilities Toyota declares for this car.

Use for: what car is this? when was it registered? is the connected subscription still active? can it be locked remotely? Capability flags are indicative only — see remote_capabilities.note.

Doors, windows, trunk, hood, lock state, lights and rear-seat reminder.

Use for: is the car locked? are windows or doors open? did I leave the lights on? Lock state is pushed by the car when parked and can lag — always cite freshness.vehicle_reported_at when answering. Warning lights are NOT here; use toyota_get_health for alerts and maintenance.

Remaining fuel, driving range and (when applicable) battery state.

Use for: how much range is left? how full is the tank? is it charging? On self-charging full hybrids Toyota exposes no battery data — the response says so explicitly in battery_note instead of returning nulls.

Total distance on the odometer.

Use for: how many kilometers/miles are on the car?

Plug-in battery: charge level, charging status, EV range, time to full, schedules.

Use for: is it charging? how much EV range? when is the next scheduled charge? Plug-in hybrids and electric vehicles only — other powertrains get an explicit "not applicable" error (use toyota_get_energy).

Last parked position of the vehicle: coordinates, Google Maps link, address.

Use for: where is the car? The address needs the server started with --addresses osm or fr. The position updates only when the car parks — while driving it shows the last parking spot; cite freshness.vehicle_reported_at when answering.

Most recent trip: distance, duration, consumption, hybrid mode split, places.

Use for: how was the last trip? what did the last drive consume? Start/end addresses need the server started with --addresses osm or fr.

Individual trips over a recent window, newest first.

Use for: list this week's trips, when did the car last drive? For averages over a period, prefer toyota_get_trip_summary. For windows beyond 92 days, use toyota_get_trip_summary.

Aggregated driving statistics over a rolling window or a calendar period.

Use for: average consumption over the last 7 days, EV-mode share this month, total distance this year. Consumption is recomputed over the whole window (total fuel vs total distance), not a mean of daily means. Pass period to match the app's calendar figures.

Warning lights, oil indicators, recent notifications and the service history.

Use for: any alerts on the car? when was it last serviced? Toyota exposes service history, not upcoming maintenance deadlines.

Remote pre-conditioning state (running or stopped, temperatures) and the saved preset a remote start would apply (target temperature, duration, defrosters, heated seats).

Use for: is the climate running? what temperature is the preset? Starting or stopping it is done with toyota_start_climate / toyota_stop_climate when remote commands are enabled.

Cheapest stations selling a given fuel around the car's last parked position.

Use for: where can I fill up cheaply near the car? France only: prices come from the French government open-data feed and need the server started with --addresses fr.

Re-fetch status, telemetry and location from Toyota's cloud.

Rarely needed — the car pushes new data only at ignition-off, so answers refresh themselves as the car is driven. Use only when the user just parked and wants the very latest position or status. This reads Toyota's cloud; it never wakes the car.

Lock the doors, then verify against the state the car reports.

Only when the user explicitly asked to lock the car. Call with confirm=false first when in doubt; the report says whether the car confirmed the new state.

Unlock the doors, then verify against the state the car reports.

Security-sensitive: only when the user explicitly asked to unlock the car in this conversation, never on your own initiative. Preview with confirm=false unless the user already confirmed.

Lock the trunk only, then verify against the state the car reports.

Unlock the trunk only (doors stay locked), then verify against the state the car reports. Only on the user's explicit request; preview with confirm=false unless the user already confirmed.

Flash the hazard lights briefly so the user can spot the car — silent. Verified by the car reporting back.

Sound a short horn signal to locate the car — audible to everyone around it; prefer toyota_find_car unless the user asked for sound. Verified by the car reporting back.

Close all power windows, then verify against the state the car reports. Not every model supports it; Toyota answers 'vehicle not supported' when not.

Start remote pre-conditioning with the saved preset (duration, defrosters, seats).

On a hybrid this runs the engine — never start it in an enclosed space. Only when the user explicitly asked; preview with confirm=false unless the user already confirmed. Verified against the climate state the car reports.

Stop remote pre-conditioning, then verify against the climate state the car reports.

Only when the user explicitly asked; preview with confirm=false when in doubt.

Start charging the plug-in battery immediately, ahead of any schedule.

Plug-in hybrids and electric vehicles only; the car must be plugged in. Only when the user explicitly asked; preview with confirm=false when in doubt. Verified against the charging state the car reports.

Ask the car to report its current state right now, then re-read doors and climate.

The passive reads only see what the car pushed when it parked; this sends the same wake request the MyToyota app uses. It costs the car a little 12 V battery and cellular time — use it when the user needs the state as of now, not routinely.