# Timezone Offset Engine MCP > Timezone Offset Engine calculates the exact time difference between any two IANA-compliant zones at a specific moment. It handles all Daylight Saving Time (DST) transitions worldwide, using the full IANA database for guaranteed accuracy. Your AI client calls this tool to get precise offsets in hours and minutes, ensuring your scheduling or data logic never gets confused by DST changes. ## Overview - **Category:** productivity - **Price:** Free - **Tags:** timezone, dst, datetime, scheduling, iana-database, global-time ## Description You're dealing with time zones? Forget what your AI client thinks it knows. This **Timezone Offset Engine** is built for precision. It runs on the full IANA timezone database, so you never worry about Daylight Saving Time messing up your logic. Your agent uses `get_timezone_offset` by passing two specific IANA zone names and an optional ISO 8601 timestamp. The tool immediately spits out the exact offset in hours and minutes for that moment, telling you if it's even observing DST. It’s pure, verifiable time math. When you need to figure out how far apart São Paulo and London are on a specific day—say, July 15th—you just pass those two zones and the date. The engine handles every rule change that might happen between them. You don't gotta guess what DST does; it tells you exactly where the time difference lands at that precise moment. If your workflow requires checking if a zone is currently running on DST, the tool reports that status directly when you call `get_timezone_offset`. It tells you whether each specified location is observing Daylight Saving Time for the requested timestamp. This means your agent knows instantly if it needs to adjust its internal logic for those zones. The engine lets you calculate local times in two different zones based on a single starting point. You give it one timestamp, and it figures out what time that'll be locally in both of the specified regions. It’s perfect for scheduling tasks across multiple continents. It handles date ranges that cross major DST boundaries flawlessly. If your calculation spans days where the rules change—for example, crossing a spring forward or fall back day—the offset remains valid because the system uses the comprehensive IANA database. You're safe from those tricky mid-year rule changes. When you call `get_timezone_offset`, it gives you more than just an offset number; it delivers that precise offset in hours and minutes, along with a boolean flag confirming if each zone is currently observing DST at the specified time. This level of detail keeps your data pipelines running clean and accurate. You'll use this when you need to verify complex time differences across international lines. It works by consuming two IANA timezone names—like `America/New_York` and `Europe/Paris`—and an optional ISO 8601 datetime string. The tool takes these inputs and returns the exact offset, which is crucial for any scheduling agent or data processing pipeline that can't afford to get confused by time changes. You pass two zones and a specific timestamp when you want to determine the precise offset between them at that date. This ensures your system calculates the difference correctly even if one zone observes DST while the other doesn't, or if both are changing rules on the same day. The function determines the local time in two different zones from just one starting timestamp. You give it a moment, and it spits out what time that is locally for both specified locations simultaneously. This feature eliminates guesswork when coordinating events across time zones. This tool's ability to handle cross-boundary checking means you don't have to write complex date logic yourself. If your data crosses the line of a major DST transition, like moving from one calendar year to another or spanning an entire seasonal change, the offset calculation stays solid and reliable. ## Tools ### get_timezone_offset Pass two IANA timezone names and an optional ISO 8601 datetime. The engine returns the precise offset in hours/minutes and DST status. Use this when you need to verify time differences. ## Prompt Examples **Prompt:** ``` What is the time difference between São Paulo and London on July 15, 2025? ``` **Response:** ``` Offset: +4 hours (London is in BST/DST, São Paulo is not). ``` **Prompt:** ``` If it's 9am in Tokyo right now, what time is it in New York? ``` **Response:** ``` Tokyo 09:00 JST → New York 20:00 EDT (-13 hours). ``` **Prompt:** ``` Will the offset between Berlin and Sydney change in March 2025? ``` **Response:** ``` Yes. Check March 1 vs March 31 — DST transitions in both hemispheres change the offset. ``` ## Capabilities ### Determine Offset by Date Pass two IANA timezone names and a specific date/time to calculate the exact offset between them. ### Check DST Status The tool reports whether or not each specified zone is currently observing Daylight Saving Time at the requested moment. ### Calculate Local Times You can determine the local time in two different zones based on a single starting timestamp. ### Cross-Boundary Checking It handles dates that cross major DST transitions, ensuring the offset calculation remains valid even when rules change mid-year. ## Use Cases ### Scheduling an international deadline A global program manager needs to set a submission deadline for London and Sydney. They ask their agent: 'What is the offset between Europe/London and Australia/Sydney on November 1st?' The agent calls `get_timezone_offset`, gets the accurate offset, and informs the manager of the precise time difference, avoiding confusion over changing rules. ### Aligning multi-region log files A DevOps engineer reviews server logs from two different data centers (America/Chicago and Asia/Shanghai). They ask their agent to calculate the offset for a specific failure time. The agent uses `get_timezone_offset` with the timestamp, giving the exact hours difference needed to correctly sequence the events. ### Comparing event times across zones A data scientist needs to compare two marketing campaign start dates in New York and São Paulo. They ask their agent: 'What's the offset between America/Sao_Paulo and America/New_York on July 15?' The agent runs `get_timezone_offset`, confirming the precise difference, which is critical for reporting accurate global metrics. ### Validating a complex API requirement A backend developer needs to write code that checks if a user input time falls within an acceptable window across two zones. They use `get_timezone_offset` to determine the required offset boundaries for their validation logic, ensuring the client-side and server-side clocks match. ## Benefits - Stop worrying about Daylight Saving Time shifts. The `get_timezone_offset` tool guarantees the offset calculation is correct for any date, even when zones transition between standard and daylight time. - Keep your data pipelines clean. Instead of guessing time differences, you use this tool to get a verifiable offset in hours and minutes, which keeps all synchronized records accurate. - Schedule meetings with confidence. You can feed the agent two location names and a date, and it returns the precise offset for that specific moment, letting you suggest meeting times that work globally. - Handle global logs without breakage. If your data comes from multiple time zones (e.g., Tokyo and London), `get_timezone_offset` tells your agent the true difference, so your records align correctly. - Maintain code reliability. By calling `get_timezone_offset`, you offload the complex logic of IANA timezone rules to a dedicated engine, making your application less brittle. ## How It Works The bottom line is: you get a verifiable time difference that accounts for global time rules and Daylight Saving Time changes. 1. Your AI client calls `get_timezone_offset`, providing two IANA zone names (like "Asia/Tokyo" and "America/Los_Angeles"). 2. You pass an optional ISO 8601 datetime string to specify the exact moment for calculation. 3. The engine runs the query, returning the precise offset in hours/minutes, along with DST status flags for both zones. ## Frequently Asked Questions **How do I use get_timezone_offset to check DST?** Just call `get_timezone_offset` and pass an optional ISO 8601 datetime. The tool response includes a flag for each zone, confirming if it's operating under Daylight Saving Time at that specific time. **Can get_timezone_offset handle non-standard zones?** Yes. It supports all 400+ IANA timezones, meaning it can calculate offsets for nearly any location on Earth, provided you use the correct zone identifier. **Is get_timezone_offset better than simple date math?** Absolutely. Simple math fails when DST changes occur. `get_timezone_offset` uses the full IANA database to calculate time offsets accurately, regardless of how complex the zone rules are. **What format should I use for get_timezone_offset's date input?** Use ISO 8601 datetime format (e.g., '2025-07-15T12:00:00Z'). This gives the engine the specific moment it needs to calculate the offset for. **How does `get_timezone_offset` handle malformed or non-existent IANA zone names?** It returns a specific error message detailing the exact zone name that failed validation. The engine won't guess; it throws an explicit failure when a provided timezone doesn't match the official database. **What is the expected performance or rate limit when calling `get_timezone_offset` frequently?** The server handles high-volume requests efficiently. While specific operational limits depend on your Vinkius subscription tier, it's engineered for reliable, enterprise-level data throughput. **Can `get_timezone_offset` calculate the time difference without providing an ISO 8601 datetime?** Yes. If you omit the specific date and time input, it calculates the maximum potential offset range between the two zones based on their established rules. **What underlying library does `get_timezone_offset` use, and why should I trust its calculations?** It uses Luxon with the full, maintained IANA timezone database. This isn't a simple calculation; it relies on globally vetted standards for timekeeping. **Does it handle Daylight Saving Time?** Yes. This is the primary reason this tool exists. It calculates offsets at the exact moment you specify, correctly accounting for all DST transitions worldwide. **What datetime format should I use?** ISO 8601 format: YYYY-MM-DDTHH:mm:ss (e.g. '2025-07-15T14:00:00'). If omitted, the engine uses the current moment. **How many timezones are supported?** All 400+ IANA timezone identifiers, including regional variants like America/Argentina/Buenos_Aires and special zones like UTC and GMT.