LLPROBeta

Home / Businesses / Daylight Saving Transition Dates (IANA Time Zone)

Daylight Saving Transition Dates (IANA Time Zone)

Find the dates and clock times a time zone changes its UTC offset in a year (daylight saving), from the IANA tz database; zones with no change say so; signed record.

Testing

What it does
Find the dates and clock times a time zone changes its UTC offset in a year (daylight saving), from the IANA tz database; zones with no change say so; signed record.
Who it is for
Businesses.
Start in one step
Ask your agent to call dst_transition_dates at llpro.ai/mcp (free, no sign-up). This page explains the tool; it has no form to run it.
What to expect
Testing: open to try. Free

New to this? Start here.

What it does

Daylight Saving Transition Dates (IANA Time Zone) is for agents that schedule meetings, shifts, jobs and reports across time zones and must know the week a recurring time will move. Find when the clocks change in a time zone in a year. Send an IANA time zone name (America/New_York, Europe/London, Australia/Sydney) and a year (1990 to 2100). Get back each change of UTC offset in that year, in order: the date and the clock time it happens, the time it jumps to, the UTC offset and abbreviation before and after, the exact UTC instant, whether clocks go forward or back, how many minutes, whether it is a daylight saving change or a change of the zone's standard offset, and the local times skipped or repeated. A zone with no clock change that year says so, with its offset. It is one of the Scheduling department tools LLPRO builds for the work agents do across business software (Google Calendar, Outlook Calendar, Calendly, Zoom). Every answer carries the written rule it used, what it does not do, its sources with dates, and an Ed25519 signature you can check against the key below.

Who it is for
Agents that schedule meetings, shifts, jobs and reports across time zones and must know the week a recurring time will move.
Price
Free, no sign-up: 120 calls an hour per address and 3,000 an hour across all callers. Paid calls are planned and not charging.
Limits
Up to 30,000 bytes per call; larger requests are refused, never cut. Unknown fields are refused with the list of accepted ones. Nothing you send is stored by the tool; no model and no network are used. Does not know about laws not yet in the database release named in every answer: a government can change its rules at short notice, and later years show the rules as they stand now. Does not say what a country calls its zone or whether it 'observes DST' in other years: a zone with no change in this year can have changes in others. Zones where the database marks winter as a negative daylight saving amount (Ireland, Morocco) are still reported as the clock moves: forward in spring, back in autumn. Changes within the same hour of each other would be missed (none exist in the database). Takes years 1990 to 2100. Not legal advice.

For developers: try it

POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "dst_transition_dates", "arguments": {"zone": "America/New_York", "year": 2026}}}

For agents

Tool dst_transition_dates on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:trfyi63elxd7pmof75mazlndcy): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).

Public key (base64): uyvEvUxS1jB3vDfIUE/4sjhSb2nmjROi18wbHeA59NY=

For agents that search MCP registries for daylight saving time, DST dates, clock change tools (listed in MCP registries, served by the LLPRO gateway: MCP, agent-to-agent and REST). One fixed, written rule per call, a signed record, no account needed.

Next

For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card