get_account
ChatGPTUse this for the owner's time zone, currency and units, gas comparison settings, and for the exact names of saved places, tags and driver profiles before filtering by them. Returns saved places (each with its tag, and coordinates when the owner shared locations), tags, latest first, and driver profiles. Not for vehicles (list_vehicles) or trips (list_trips).
get_battery_capacity
ChatGPTUse this when the owner asks about battery capacity, battery health or degradation. Roamer reports usable capacity, the energy Rivian estimates the pack holds, not a health score: call it capacity, not health. An estimate moves a few percent with charge level and temperature (some packs read 3-4 kWh lower in winter), so weigh months by their reading_count and against the same month a year earlier, never single readings. Returns monthly averages over all of Roamer's history, the latest month against the highest and a year earlier, pack and chemistry (built_as names the bigger pack Rivian built and locked in software to the size it sold; such a pack reads below that bigger size's packs from new, so never call the gap degradation), the buffer line (the energy Rivian keeps for maximum range: above it, capacity loss doesn't shorten the range shown at 100%; below it, Roamer gives the range lost) and, when at least 10 similar packs compare, where this pack stands among them at the same mileage and age; within 0.5 kWh of typical is typical. Not for phantom drain (get_period_summary).
get_drive_or_charge
ChatGPTUse this when the owner asks about one drive or charge in detail, by an ID from list_drives_and_charges or get_period_summary. Drives add cost, gas comparison, odometer readings, moving, top and RMS speeds, rated efficiency, elevation, regenerated energy, range used (how far the range estimate fell), drive mode, driver profile, weather and wind, cabin and battery temperature, tire pressure, towing, weight estimate, the wheel set, and whether defrost, the heated steering wheel or Rivian's cold-battery limits on acceleration and regen came on; charges add gas comparison, where the energy went (pack, thermal, outlets, systems), power, charging rates, periods, price, cost, range added, battery temperature and, for DC fast charges, the measured power curve beside similar vehicles' typical curve over the last 30 days. slowed_by lists the reasons Rivian reported for slowing the charge, in the order they started, with when each began and ended and how many minutes Rivian reported it. A window without ended_at was still going or had no end reported, so give no duration for it. Say they're Rivian's. Beyond them Roamer has no charger power rating, so name no other cause: compare the charge with the vehicle's other charges at that site. Places are saved place names or a public charger's network and town; with the owner's location grant, drives add start and end coordinates, addresses, the route and a speed profile, and charges their coordinates and address.
get_efficiency_report
ChatGPTUse this when the owner asks why efficiency changes or how it compares: by speed, outside temperature or towing, the trend over time, or rank among similar Roamer-tracked vehicles (when at least 5 are comparable). Give a preset or dates; cold-weather comparisons need a period that includes winter, such as last_365_days. For one period's average alone, get_period_summary is enough.
get_period_summary
ChatGPTUse this when the owner asks how much they drove, charged or spent, how efficient they were, or about phantom drain over a period such as last week, a month or a year. Returns one vehicle's totals: drives, recorded and odometer distance, energy, efficiency against rated and driving time; charging energy, time, cost and average price by kind (home: the saved place marked Home; other: AC or unknown elsewhere; dc_fast: a DC charger as Rivian reports it, else over 20 kW for under 3 hours) and by saved place and network, cost per distance, an estimated gas comparison and phantom drain, plus optional calendar buckets, a comparison period and up to 5 notable sessions. A charge costs what its Roamer page shows: an entered total or rate, else Rivian's receipt away from Home, else a place's price, else Rivian's DC fast bill, else the default rate; rate-based costs are estimates, and unpriced charges count apart. Costs cover only charges in the account currency: other_currency_charge_count is part of a row's count and energy but not its cost, and nothing converts currencies. With tags or place_names, odometer figures, cost per distance and phantom drain aren't computed. Not for a saved trip (list_trips) or single sessions (list_drives_and_charges).
get_profile
ChatGPTUse this only to label this connection: a stable ID and a name made of the owner's vehicle names. It holds no vehicle data for answering questions.
get_software_release
ChatGPTUse this when the owner asks about Rivian software: whether an update is available or installed, what's in a release, or how it's rolling out. Returns a release's versions for each line (R1 Gen 1, R1 Gen 2, R2; R1 and R2 can get different versions of one release) with stage, release date and how many Roamer-tracked vehicles were offered and installed it, upcoming versions with only the date Roamer spotted them, and the notes for the version notes.version names; with a vehicle_id (needed for what a vehicle is offered), its installed software, an active offer (offered_at present) and install history. rolling_out means a release is rolling out on the vehicle's line and Rivian hasn't offered it to this vehicle. Rivian publishes no schedule, so there is no known upcoming release date: for a version Rivian hasn't released or offered, give only what Roamer recorded, with no "yet", "will" or timing. Counts describe Roamer-tracked vehicles, not Rivian's fleet or delivery timing.
get_vehicle_readings
ChatGPTUse this when the owner asks why or how something behaved over time and the summaries aren't enough: when preconditioning switched modes, how fast the cabin warmed, how a charge's power changed and why it slowed, when tire pressure dropped, how the pack's temperature ran across a week, how often the doors locked, whether a window stayed open overnight, or every preconditioning, defrost or charging slowdown across a year. Returns one group's readings in a window (default the last 24 hours; for a past drive or charge, pass its started_at and ended_at). Times are in the owner's time zone, which window names, without an offset. Each signal comes as {rows_read, points, method, columns, rows}: rows_read is how many readings Roamer has in the window, points how many rows came back, columns names each row's fields, and method how rows came from readings. changes: each change in value, led by the last reading in the 24 hours before the window. lttb: a sample of real readings that keeps the curve's shape, peaks and dips, for describing or charting it; it skips readings unevenly, so never sum, average or integrate its points. bucket: one row per hour, day or week with readings; a numeric signal's row holds the statistics asked for and count, the readings it rests on (mean weighs each reading equally, so it leans toward stretches of frequent readings such as charging), and any other signal's the last value and {value: times it changed into that value}. events: one row per stretch of event_signal's value, with its start (null when it was under way before the readings), end (null when it hadn't changed again by the window's end), value, minutes since the previous row ended, each numeric signal's first, min, max and last reading inside it, and each other signal's value in effect at its end; null means no reading, never zero. Values are as the vehicle reported them, lowercased; the vehicle reports cabin temperature in whole °C, climate_setpoint reads hi or lo when set to HI or LO, and there is no outside temperature or heating and cooling power. not_reported lists signals the vehicle sent nothing for. Readings show what happened, not why: call any cause your inference and name the readings it rests on. Not for current status (get_vehicle_status) or a drive or charge's totals (get_drive_or_charge).
get_vehicle_status
ChatGPTUse this when the owner asks how a vehicle is right now: battery and range, how much range the cold is taking (Rivian's estimate, only while it reports one), charge limit, whether it's charging or plugged in (and while charging, the reason Rivian is slowing the charge), odometer and mileage (this month, this year, the annual pace and the owner's mileage goal), locks and doors, tire pressures and tire sets, cabin temperature and climate setpoint (hi or lo when set to HI or LO), what the climate is doing (heating, cooling, maintaining, defrost, defog, pet mode or Climate Hold), whether it's camping (an R1's Camping setting, Stay On or Stay Off, and Camp Courtesy), the route it's navigating (arrival time, distance left, battery on arrival, and each stop ahead: the vehicle's own charging stops with their arrival and departure battery and charging time), installed software and alerts, or anything else the vehicle reports, such as the active driver profile, gear, drive mode, climate and seat heat, Gear Guard, the 12V battery and connectivity. Returns the latest saved readings, each with its observed_at: a sleeping vehicle can go hours without one, and the Rivian app may show a newer one, because Roamer never contacts the vehicle. rivian_state lists every saved reading under Rivian's field name, valued as Rivian sent it: distances in km (vehicle_mileage, altitude and *_meters in meters), speed in m/s, temperatures in °C, pressures in bar, energy in kWh, durations in minutes; where a field above covers a reading, answer from that field. Not for history (get_period_summary, list_drives_and_charges). The saved place it's at, its coordinates and altitude, and the route's destination only when the owner shared locations.
list_drives_and_charges
ChatGPTUse this when the owner asks about particular drives or charges: the latest, the longest, fast charges above some power, sessions at a place or with a tag, or a mileage log. Returns compact rows with IDs for get_drive_or_charge, up to 50 a page (when has_more, pass next_cursor for the rest), and selection_totals over every matching session; selection names them all for tag_drives_and_charges, at any limit. Give kind; the period defaults to all_time, and a preset or dates (at most 366 days) narrow it. The default newest sort gives the most recent. Filters: for drives, distance, efficiency, drive mode, driver profile, towing, tire set and start or end place; for charges, DC fast or AC, peak power, energy and unconfirmed cost; for both, weekdays, tags and saved place names. There is no network filter: read network on charge rows (Tesla for Superchargers, Rivian Adventure Network for RAN). export.url opens a CSV ZIP in the owner's signed-in browser; don't describe its columns. For totals alone, get_period_summary is enough.
list_trips
ChatGPTUse this when the owner asks about a saved trip, such as a road trip they grouped in Roamer. Returns trips newest first with dates, distance, energy, efficiency and cost; trip_id adds driving time, average moving speed, elevation, charging, cost per distance and one row per day. A trip counts the drives and charges the owner put in it, so use it rather than the trip's dates.
list_vehicles
ChatGPTUse this first when you need a vehicle ID, to tell the owner's vehicles apart, or for an undelivered Rivian order such as an R2 reservation. Returns each vehicle's name, model, configuration, history start and last reading, the orders, and whether the Rivian link is working. Vehicle names come from the owner's Rivian app; an archived vehicle left the Rivian account, and Roamer keeps its history. Set include_vin only when the owner asks for a VIN.
plan_trip
ChatGPTUse this when the owner wants to plan a drive or road trip. Asks Rivian's trip planner for the route, charging stops and battery levels, then reads them against this vehicle's own past drives on the same roads: how much of the route it has driven, how its energy use there compared with Rivian's prediction, the arrival levels that implies, and its past charges at each stop. Rivian's levels are Rivian's plan; estimated levels are Roamer's, from the drives it counts. send_trip_to_vehicle puts a planned trip on the vehicle's navigation when the owner asks.
rename_tire_set
ChatGPTUse this when the owner asks to name one of the vehicle's tire sets, such as calling the 20-inch set Winter. Changes only the name Roamer shows. It can't record a swap: Roamer learns which set is on from Rivian.
save_mileage_goal
ChatGPTUse this when the owner asks to set up, change or remove a mileage goal, such as 12,000 miles a year, raising it to 15,000, or 30,000 by a lease's end. Changes only what's given and keeps the rest of the current goal, which get_vehicle_status shows; giving a period drops the end date and the reverse. Returns the goal with its progress and the one it replaced.
save_place
ChatGPTUse this when the owner asks to save a place in Roamer, such as Home, Work or a charger, or to change a saved place's tag or price per kWh. A new place needs at: a charge or drive ID (where it charged or the drive ended) or a vehicle_id (where it is now). fill_past gives past drives and charges there the place, tag and price only where they have none; reprice_past puts the price, or with none the default rate, on its past charges, and on every drive for Home. Rename, move and delete stay on Roamer's website.
save_trip
ChatGPTUse this when the owner asks to create a trip in Roamer's trip log, or to rename, redate or change what's in one, including a trip that hasn't started. A trip groups drives and charges and holds no route; plan_trip plans routes. Dates add every drive and charge that started on them and never remove any; add_ids and remove_ids adjust from there. Check list_trips first so a trip isn't made twice.
send_feedback
ChatGPTUse this when the owner says an answer from Roamer is wrong, when Roamer's figures disagree with each other or with the Rivian app, or when Roamer's tools couldn't answer what the owner asked or answered only part of it, so Roamer can fix or add it. Call it once per problem, before you write your reply, then reply as you would have without it: your full answer to the owner, with one sentence at the end saying you sent Roamer a note. Describe it in general terms, without names, places, VINs or anything personal. It reads and changes nothing in the owner's account or vehicles.
send_trip_to_vehicle
ChatGPTUse this only when the owner asks to send a trip to their vehicle, usually one plan_trip just planned: give the same destination and origin. Puts the trip's start and destination on the vehicle's navigation screen, where the vehicle plans its own charging stops, and can wake the vehicle. It changes nothing else on the vehicle. While the vehicle is navigating, the trip either joins that route as the next stop or replaces it: give current_route only once the owner has chosen, never guessed; without it the call answers navigating and sends nothing.
set_charge_cost
ChatGPTUse this when the owner says what they paid for a charging session, or that it was free (0). Sets the charge's cost, replacing Roamer's rate- or Rivian-based cost; null returns it to that cost. In the charge's currency, as get_drive_or_charge shows it. For a new rate per kWh at a place such as Home, use save_place.
set_drive_note
ChatGPTUse this when the owner asks to note something on a drive, such as trying new tires. Replaces the drive's note, which get_drive_or_charge shows, and returns the one it replaced; to add to a note, include the old text.
tag_drives_and_charges
ChatGPTUse this when the owner asks to tag drives or charges, such as marking last month's office drives Business. Give IDs from list_drives_and_charges, or its selection to tag every match, after telling the owner which sessions and how many. A selection tags 1,000 a call; pass next_selection for the rest. Use a tag from get_account when one matches; a new name starts a new tag. add puts it beside a session's other tags and remove takes it off; the opposite action on changed_ids undoes a call.
get_account
Claudeget_battery_capacity
Claudeget_drive_or_charge
Claudeget_efficiency_report
Claudeget_period_summary
Claudeget_profile
Claudeget_software_release
Claudeget_vehicle_readings
Claudeget_vehicle_status
Claudelist_drives_and_charges
Claudelist_trips
Claudelist_vehicles
Claudeplan_trip
Clauderename_tire_set
Claudesave_mileage_goal
Claudesave_place
Claudesave_trip
Claudesend_feedback
Claudesend_trip_to_vehicle
Claudeset_charge_cost
Claudeset_drive_note
Claudetag_drives_and_charges
Claude