well_get_travel_time

io.github.WellApp-ai/well-mcp · Verify this server

Get how long one trip takes and how far it is, from Google Maps: "the drive to the 10:00 meeting", "le trajet jusqu'au match de samedi". Call it once per event that has a location when the person asks for the travel time. Pass `destination`: the event's location copied as the event or the mail states it. Pass `origin` only when the person has an event with a location just before it that day (give that location) or when the person gave a start address; otherwise leave it out and the trip starts from the workspace's own address. Leave `mode` out for a car trip unless the person named another way. Pass `departure_at` when the time the person leaves is known, so a car trip reads traffic. An event with no location gets no call: say its travel time is unknown. The tool runs at most 12 times per turn. Returns `status` "found" with `duration_minutes`, `distance_km`, `mode`, `origin_kind` and `origin`, or "no_route" when Google Maps found no route. Give the duration as the tool returns it, say it comes from Google Maps, and when `origin_kind` is "workspace_address" say the trip starts from the workspace's address. Never estimate, compute or recall a travel time or a distance the tool did not return. On a failure, `error_reason` is one of "origin_required" (no start was given and the workspace has no address on file: ask the person where they leave from), "call_limit_reached" (this turn already asked enough trips), "daily_limit_reached" (the person or the workspace reached today's limit) or "travel_time_unavailable" (the travel time cannot be read now). Then say in the person's language that the travel time is not available and why, and give no figure. When the token authorizes one workspace, call this directly — no workspace call is needed first. When it authorizes several, this read will not guess which one you mean: pass `workspace_id` on the call.