Timezone Lookup Skill

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 Lookup Skill Skill →

The tool

Once your client is connected to the VerveKit server, this appears in its tool list as TimezoneLookupSkill. 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.

{
  "name": "TimezoneLookupSkill",
  "arguments": {
    "city": "Harare"
  }
}

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

Connecting

One server URL covers every skill 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": {
    "vervekit": {
      "url": "https://api.vervekit.com/v1/mcp"
    }
  }
}

https://api.vervekit.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.

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.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20

{
  "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.

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.

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 Lookup Skill

Set up Timezone Lookup Skill on VerveKit, or reach the same source a different way. Your VerveKit account and credits work on all of them — one key, one balance.

Related

Pages that use this skill:

• GraphQLPlatform

More in Data Lookup: