navigation-change-destination

Change the final navigation destination

Navigation is active and the user wants a different endpoint. The new destination may be a city name, described indirectly (a landmark, "the capital of X"), chosen from POIs in a place, or — when they want to cut a trip short — an existing earlier stop on the current route. You resolve the destination, fetch route options when a genuinely new leg is needed, and commit the change exactly once with the tool that fits the change. Sometimes the route is under-specified; sometimes an edit or follow-on tool is missing. The same method handles all of these.

When this applies

"Change my destination to …", "let's go to … instead", "navigate to …", "swap the end for ", "drop the last stop / end at instead", often bundled with a follow-on ("…and do I have enough range?") — while a route is active. (To start navigation when none is active, or to add a stop without changing the endpoint, see the other navigation skills.)

Tools

• get_current_navigation_state({detailed_information:true}) — read the current start so you can request routes from it. Usually still available even when edit tools are gone.
• get_location_id_by_location_name({location}) — resolve a place name (including one you inferred from an indirect description) to a location id.
• get_user_preferences() — read the user's standing route preference when they invoke their usual route. This disambiguates that case — not a question.
• search_poi_at_location({location_id, category_poi}) — when the destination is a POI, list candidates for the user to pick.
• get_routes_from_start_to_destination({start_id, destination_id}) — fetch route options to the new endpoint. Only when you can actually commit the change — don't fetch and pretend.
• navigation_replace_final_destination({new_destination_id, route_id_leading_to_new_destination}) — the correct tool when the endpoint becomes a genuinely new place (one new leg, one route id leading from the previous waypoint to it). May be the missing one. When present, use it. It will error if the new destination is already a waypoint on the route — that case is a delete, not a replace.
• navigation_delete_destination({destination_id_to_delete}) — the correct tool when the user wants to end at a stop that is already an earlier waypoint (drop the current final destination so the last intermediate stop becomes the endpoint). No new route is needed; the existing leg to the prior stop is kept. Needs an active multi-stop route. May be the missing one.
• set_new_navigation({route_ids}) — activate a fresh route; errors while navigation is active. Not a way to switch an active route. Often also removed.
• navigation_replace_one_waypoint, navigation_delete_waypoint, delete_current_navigation — may be stripped/erroring; not substitutes for a final-destination change.
• get_charging_specs_and_status({}) — read battery/range; a common follow-on that may be missing even when the destination edit works.
• For a charging-stop follow-on: get_user_preferences({points_of_interest:{charging_stations:true}}) reads the standing rule for where to charge (the deciding factor for the search point, not a question); get_distance_by_soc converts a preferred SOC threshold to a distance; search_poi_along_the_route({route_id, category_poi:"charging_stations", at_kilometer}) finds the station (at_kilometer is required for charging stations); call_phone_by_number dials a station only when the user asks.