Docs/Sources/Timezone Grounding Data for AI Agents

Timezone Grounding Data for AI Agents

Lookup timezone data

OperationalCredits 2 per callp50 385msData Lookup

Overview

Pass either a city name or a standard IANA timezone string to retrieve the current date, multiple clock formats, and the UTC offset in minutes. Paid plans add Unix timestamps, daylight saving time flags, and seasonal transition schedules.

Live Test Timezone Grounding Data for AI Agents Source →

The tool

Once your client is connected to the VerveContext server, this appears in its tool list as TimezoneGroundingDataforAIAgents. It is read-only and open-world — it fetches and never mutates anything on your side — so most clients call it without asking you to confirm.

Tool call
{
  "name": "TimezoneGroundingDataforAIAgents",
  "arguments": {
    "city": "Harare"
  }
}

You do not name the tool yourself; the model picks it. Asking about Harare in the terms this source covers is enough for it to reach for TimezoneGroundingDataforAIAgents on its own — naming it explicitly also works, and is the way to force the call.

Connecting

One server URL covers every source in the catalog, including this one. Authorization is OAuth: the client opens a browser once, and there is no key to paste into a config file.

{
  "mcpServers": {
    "vervecontext": {
      "url": "https://api.vervecontext.com/v1/mcp"
    }
  }
}

Per-client setup — Claude, Cursor, VS Code, ChatGPT — is on the MCP setup page.

Arguments

These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made. Premium arguments are accepted on every plan but only take effect on plans that include them.

ArgumentTypeDescription
cityRequiredstringThe city name for which you want to get the data (e.g., Harare)

What the model gets back

The result carries a structuredContent object matching the tool's declared outputSchema, so a client reads fields without parsing prose. status is "ok" and error is null on success; a null field means the value was not available for that input, not that the call failed.

Result
{
  "status": "ok",
  "error": null,
  "data": {
    "timezone": "Africa/Harare",
    "timezone_offset": 120,
    "date": "2025-12-17",
    "time": "00:30",
    "time24": "00:30:23",
    "time12": "12:30:23 AM",
    "day": "Wednesday",
    "month": "December",
    "year": "2025",
    "unix": "1765924223",
    "dst": false,
    "dst_start": "2025-12-17 00:30:23",
    "dst_end": "2025-12-17 00:30:23",
    "dst_name": "CAT"
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

FieldTypeExampleDescription
timezonestringAfrica/HarareIANA timezone identifier for the city
timezone_offsetnumber120Timezone UTC offset in minutes from GMT
datestring2025-12-17Current date in YYYY-MM-DD format
timestring00:30Current time in HH:MM format
time24string00:30:23Current time in 24-hour HH:MM:SS format
time12string12:30:23 AMCurrent time in 12-hour AM/PM format
dayPremiumstringWednesdayCurrent day of week name
monthPremiumstringDecemberCurrent month name
yearPremiumstring2025Current year as string value
unixPremiumstring1765924223Current Unix timestamp in seconds
dstPremiumbooleanfalseWhether daylight saving time is currently active
dst_startPremiumstring2025-12-17 00:30:23DST start date and time in full format
dst_endPremiumstring2025-12-17 00:30:23DST end date and time in full format
dst_namePremiumstringCATDaylight saving time zone abbreviation

Why ground on it

A model can produce something that looks like this answer from its training data, and be confidently out of date or simply wrong. This source returns the current value in a shape you can check, which is the difference between an answer you can cite and one you have to hedge.

Point an evaluation at timezone: it is the field most worth pinning a claim to, and it is either present and current or absent — never plausibly invented.

Failure modes

Errors come back as tool errors carrying a sentence the model can act on, not a bare status code. Error handling covers the full list.

StatusWhat it means
400 / 422The arguments did not validate. The message names the offending one.
401The OAuth session is invalid or expired — reconnect the server.
403Blocked by a key restriction or an IP allow-list. Never a bad identity.
404This source is not part of VerveContext. Check the catalog.
429Out of credits, or a brief rate limit. The message tells them apart.

A call costs 2 credits each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.

Use cases

World Clock Dashboards
Remote work platforms query employee cities to display current local times in 12-hour or 24-hour formats across distributed teams.
Travel Itinerary Display
Flight and hotel booking services convert destination cities into local arrival dates and formatted times for passenger itineraries.
Meeting Availability Coordination
When participants choose their home city, calendar software queries the minute offset to convert mutual open slots into local meeting times.
Scheduled Notification Delivery
Marketing automation platforms check subscriber time zones before dispatching campaigns so messages arrive during standard local daytime hours.

Other ways to use Timezone Grounding Data for AI Agents

Set up Timezone Grounding Data for AI Agents on VerveContext, or reach the same source a different way. Your VerveContext account and credits work on all of them — one key, one balance.

Call it as a REST APIOne HTTPS endpoint and an x-api-key header, with SDKs for Node, Python and .NET.APIVerve →Reference →
Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.VerveKit →Reference →
Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheets →Reference →

More in Data Lookup:

Was this page helpful?