resolve_local_time

com.tttkmbb/calcgrid · Verify this server

Use this when you must safely turn a named-zone local time into an instant, validate a scheduled time around a daylight-saving transition, or preserve every possible interpretation instead of silently choosing one. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when the input already includes a numeric UTC offset or Z, the task only needs the current clock time, or latitude/longitude must first be mapped to a zone. What it computes: Resolves a local wall-clock time with pinned IANA tzdb 2026d. Returns every valid UTC candidate for a repeated fall-back time, or the exact gap and shift-forward suggestion for a nonexistent spring-forward time. Example user requests: Resolve 2026-11-01 01:30 in America/New_York and return both UTC candidates. | Does 2026-03-08 02:30 exist in New York? Show the DST gap. | 判断 Australia/Adelaide 的 2026-10-04 02:30 是否存在，并给出时区数据版本。 Inputs: local_datetime (string); time_zone (string). Complete JSON argument examples: {"local_datetime":"2026-11-01T01:30:00","time_zone":"America/New_York"} | {"local_datetime":"2026-03-08T02:30:00","time_zone":"America/New_York"} Outputs: local_datetime, time_zone, resolved_zone_id, status, candidate_count, candidates, gap, related_transition, previous_transition, next_transition, tzdb_version, dataset_version, source_url, source_sha256, coverage_note. Formula: for each zone offset o: candidate_utc = local_wall_time + o; keep candidates whose active offset at candidate_utc equals o Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/local-time-resolver with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/time/local-time-resolver.md