well_convert_time

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

Call this for any time that is stated in another time zone than the one you will write it in ("3pm New York time", "10am in Tokyo", "what time is that for me?"): never work out an offset or a daylight-saving change yourself, because Well does the calculation and your own arithmetic is wrong around the clock changes. Pass `local_time` as the wall-clock date and time, YYYY-MM-DDTHH:mm with no offset and no Z, and `from_timezone` as the IANA zone that clock is in. Leave `to_timezone` out to convert into the user's own time zone; pass it to convert into another zone. Returns `instant_utc`, `from` and `to`. Each of `from` and `to` holds the `timezone`, the `local_time` with its UTC offset on that day, and the `utc_offset`. Use `to.local_time` as the start of a calendar event: its offset is already right. A clock time that does not exist (the hour skipped when clocks go forward) moves forward by the gap, and one that happens twice (the hour repeated when clocks go back) is the first of the two. When that happens the result carries `adjustment` ("shifted_forward" or "earlier_of_two") and `note`, a sentence for the user: tell the user what it says, in the language of the conversation, and use the returned time. On a normal time `adjustment` and `note` are absent. On `success` false, `error_reason` says why and `error` is a plain sentence. "unknown_timezone": the zone name is not an IANA name. "invalid_time": local_time is not a real date and time. "user_timezone_unknown": no time zone is known for the user, so ask them which one they are in and call again with to_timezone set to their answer. In a scheduled run no one can answer: report that the time zone is unknown and write no timed event. Never guess a zone and never fall back to UTC. 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.