ev-trip-plan

Plan an EV trip and its charging needs

The user wants the route and charging side of a trip worked out — how far, how long, whether/where to charge, how long the charge takes, how many stops. You resolve the destination, read the battery, get routes for the preferred selection, and find/reason about a charger. The decisive judgement is whether the user is asking for information or for a car action. Some requests are pure info ("plan it and email the details", "how long would I need to charge", "how many stops to get there") — gather everything, change nothing. Others explicitly call for a car action ("navigate to X with a charging stop", "replace my destination", "set it up") — then set or modify navigation as asked. The same method underlies both; only the final step differs. Under-specified requests leave genuine choices (which route, which charger) that you resolve from what the user states, asking only when truly open.

When this applies

Route + charging questions for an EV trip: "plan my trip to and email the route and charging details", "find a charger near the -km mark / where I reach %", "charge nearby before I leave, then continue", "how long to charge / how many charging stops to ", "navigate to with a charging stop", "change my destination and check if I'll need to charge". The unifying feature is reasoning about range and charging for a trip. If the request is a plain navigation change with no charging/range angle (just "take me to X", "remove a stop"), the navigation mechanics live in navigation-start / the waypoint-edit skills — come here when charging or range feasibility is part of it.

Tools

• planning_tool({...}) — optional scaffold; a malformed dependency index returns a recoverable error, so just continue with the real lookups.
• get_user_preferences({preference_categories}) — retrieve stored preferences. Use points_of_interest:{charging_stations:true} when the user defers which charger or where to charge (a stored SoC threshold or preferred provider resolves it), and navigation_and_routing:{route_selection:true} when the route choice is left to preference.
• get_location_id_by_location_name({location}) — resolve a destination or a named point to an id (use the city main name only). A "not found" result is real: surface it and ask for a correction; never invent an id.
• get_charging_specs_and_status({}) — current state of charge, range, max AC/DC power, capacity. Most of the plan depends on this. It may be removed for a task, or return a field (e.g. range, capacity) as the literal "unknown" — treat that as genuinely unavailable, not zero.
• get_current_navigation_state({detailed_information}) — read whether navigation is active and the current waypoints/routes. Read this before any navigation change to know whether to use set_new_navigation (inactive) or a waypoint-edit tool (active), and to identify which leg a charger falls on.
• get_routes_from_start_to_destination({start_id, destination_id}) — route alternatives (distance, time, tolls, fastest/shortest aliases). Start of the overall route must be the current car location.
• search_poi_at_location({location_id, category_poi, filters}) — chargers (or fast_food, etc.) AT a place. Use this when the user charges before leaving / at the current location / at a specific city.
• search_poi_along_the_route({at_kilometer, route_id, category_poi, filters}) — chargers along a route; at_kilometer is REQUIRED for charging_stations. Use this when the user charges on the way / at a km mark / where a certain SoC is reached.
• calculate_charging_time_by_soc({charging_station_id, charging_station_plug_id, start_state_of_charge, target_state_of_charge}) — charge time, computed from the current SoC at the chosen plug.
• calculate_charging_soc_by_time(...) — the inverse, when the user fixes a charging duration.
• get_distance_by_soc({initial_state_of_charge, final_state_of_charge}) — distance drivable between two SoC levels; use it to find where a buffer SoC is reached and to test whether a further stop is needed.
• convert_route_distance_and_time({route_id, time_minutes|distance_km}) — map a time on the route to a kilometre mark (e.g. to place a stop at a target arrival time) and back.
• Navigation-change tools — set_new_navigation (only when navigation is inactive), and navigation_add_one_waypoint / navigation_replace_one_waypoint / navigation_replace_final_destination / navigation_delete_waypoint / navigation_delete_destination (only when navigation is already active). Use these only when the user calls for a car action.