# convert_time_zone Use this when you need to know what time an event scheduled in one city corresponds to in another city or in UTC on a specific date. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when you need the same instant in many zones at once (use world-clock), an epoch value (use unix-timestamp), or the elapsed time between two clock times (use time-duration). What it computes: Converts a wall-clock date and time between IANA zones using pinned tzdb 2026d. It reports both offsets, the UTC instant, date changes, the source-time status and every candidate UTC instant when the input falls in a repeated hour. Example user requests: Convert 2027-01-15 09:00 America/New_York to Australia/Adelaide and show both dates. | 把 2026-07-15 09:00 纽约时间换成阿德莱德时间。 | What UTC instant corresponds to 2026-10-04 01:45 in Australia/Adelaide? Inputs: date (date, optional); time (string); from_zone (string); to_zone (string); resolution_policy (enum, optional). Complete JSON argument examples: {"date":"2026-09-23","time":"09:00","from_zone":"Australia/Adelaide","to_zone":"America/New_York"} | {"date":"2026-07-04","time":"12:00","from_zone":"America/Los_Angeles","to_zone":"Asia/Kolkata"} Outputs: converted_date, converted_time, converted_datetime, converted_weekday, from_utc_offset, to_utc_offset, from_abbreviation, to_abbreviation, utc_datetime, day_difference [days], time_difference_hours [h], source_time_status, source_candidate_utc_datetimes, applied_resolution_policy, tzdb_version, dataset_version, source_url, source_sha256. Formula: utc = date + time − offset_from(date, time); converted = utc + offset_to(utc); time_difference_hours = (offset_to − offset_from) / 60 Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/time-zone-converter with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/time/time-zone-converter.md Agent View of the PolicyLayer registry record for `convert_time_zone`. HTML page: https://policylayer.com/tools/com-tttkmbb-calcgrid/convert-time-zone ## Facts - Tool: `convert_time_zone` - Server: Calcgrid (`https://tttkmbb.com/mcp`) — https://policylayer.com/tools/com-tttkmbb-calcgrid.md - Homepage: https://github.com/https://tttkmbb.com/mcp - Risk category: Write (Medium risk) - Registry record: grade D, identity unverified - Server auth posture: open - Server CORS policy: * - Server rate-limited: no - Parameters: 5 (3 required) - Recommended policy verdict: Rate-limited ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `date` | string | no | Calendar date of the source time in from_zone (YYYY-MM-DD); defaults to the current UTC date. | | `time` | string | yes | Wall-clock time in from_zone, 24-hour HH:MM (seconds optional). | | `to_zone` | string | yes | IANA time zone to convert to, e.g. America/New_York or Asia/Tokyo. | | `from_zone` | string | yes | IANA time zone of the source time, e.g. Australia/Adelaide, Europe/Berlin or UTC. | | `resolution_policy` | string | no | How to handle a repeated or nonexistent source wall time. reject is safest; earlier/later choose a repeated-time candidate; shift_forward moves a skipped time b | Parameters from the server's own tool schema. ## Example call (MCP tools/call, JSON-RPC 2.0) ```json { "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "convert_time_zone", "arguments": { "time": "