plan_day
Turn an itinerary into one navigable multi-stop route. Provide a start and stops (each a location {lat, lon} or a free-text name to geocode, plus optional dwell_minutes time at the stop), optional depart_at (RFC 3339) for absolute ETAs, optimise: true to reorder stops for the shortest day (VROOM solver), and return_to_start. Costing "auto", "truck" (with a truck profile the whole day respects dimensional/ADR restrictions), "bicycle", "pedestrian" or "motor_scooter". Returns the stops in visit order with per-leg duration/distance and arrival/departure times, totals, and the full route geometry (polyline6). Geocoded names carry a resolution, when ambiguous is true, check alternatives and re-run with an explicit location rather than trusting the guess. Returns view_url, a mapmap.ai link that draws the answer on a map (no key needed); the link carries the stop coordinates and names.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"start": "<start>",
"stops": "<stops>"
},
"name": "plan_day"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| start | Yes | Where the day starts (name or location; `dwell_minutes` ignored). | |
| stops | Yes | The stops to visit (1–20). Visited in the given order unless `optimise` is true. | |
| truck | No | Truck profile (dimensions + ADR declaration). Requires costing "truck". | |
| costing | No | Costing model: "auto" (default), "truck", "bicycle", "pedestrian" or "motor_scooter". | auto |
| optimise | No | Reorder the stops for the shortest day (VROOM solver; requires the optimisation sidecar). Default false: visit in the given order. | |
| depart_at | No | Departure time as RFC 3339 (e.g. "2026-07-18T09:00:00Z"); when given, every ETA is also returned as an absolute timestamp. | |
| return_to_start | No | End the day back at the start (default false). |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| start | Yes | The day's starting point. | |
| stops | Yes | The stops in visit order, each with leg, ETAs and any geocoding resolution to double-check. | |
| costing | Yes | The costing the plan was routed with. | |
| summary | Yes | One-line human-readable summary of the day. | |
| view_url | No | A mapmap.ai link that draws this day plan on a map: open it or pass it on as the last line of the answer. Nothing is stored server-side and opening it needs no key; the link itself carries the stop coordinates and stop names (plus any arrival clocks, dwell times and totals) and nothing else, so anyone holding it can read those stops. Absent when the plan cannot be linked (see `view_url_note`) or the server runs with links turned off (`SN_MCP_SITE_URL` empty). | |
| depart_at | No | The departure time echoed back, when one was given. | |
| finish_at | No | Absolute end of the day (RFC 3339), when `depart_at` was given. | |
| optimised | Yes | Whether the stop order was optimised (VROOM) or kept as given. | |
| return_leg | No | The leg back to the start, when `return_to_start` was set. | |
| total_dwell_s | Yes | Total time at stops, seconds. | |
| view_url_note | No | Why there is no `view_url` (too many vehicles or stops for one link, or over the 6,000 character cap), or what the link left out to fit under the cap (arrival times, dwell times, then stop names). Relay it with the link. | |
| finish_offset_s | Yes | End of the day (last arrival + dwell), seconds after departure. | |
| total_distance_m | Yes | Total travel distance, metres. | |
| geometry_polyline6 | Yes | Full multi-stop route geometry (polyline6), hand it to the map SDK or the `route` tool consumers directly. | |
| total_travel_duration_s | Yes | Total driving/travel time, seconds. |