Meeting Time Converter Skill

Overview

Supports all IANA timezone identifiers and provides clear offset information for coordinating across multiple geographic locations.

Live Test Meeting Time Converter Skill Skill →

The tool

Once your client is connected to the VerveKit server, this appears in its tool list as MeetingTimeConverterSkill. 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": "MeetingTimeConverterSkill",
  "arguments": {
    "time": "14:30",
    "fromTimezone": "America/New_York",
    "toTimezone": "Europe/London"
  }
}

You do not name the tool yourself; the model picks it. Asking about 14:30 in the terms this skill covers is enough for it to reach for MeetingTimeConverterSkill 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"
    }
  }
}

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.

Argument	Type	Description
`time`Required	string	Time in HH:MM format (24-hour) time
`fromTimezone`Required	string	Source IANA timezone identifier timezone
`toTimezone`Required	string	Target IANA timezone identifier timezone
`date`Optional	string	Optional date in YYYY-MM-DD format (defaults to today) date

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": {
    "originalTime": "14:30",
    "convertedTime": "19:30:00",
    "date": "2026-09-18",
    "fromTimezone": "America/New_York",
    "toTimezone": "Europe/London",
    "timeDifference": 5,
    "fromOffset": "-04:00",
    "toOffset": "+01:00"
  }
}

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.

Field	Type	Example	Description
`originalTime`	string	`14:30`	Original time in source timezone
`convertedTime`	string	`19:30:00`	Converted time in target timezone
`date`	string	`2026-09-18`	The meeting date the conversion was performed for (YYYY-MM-DD), defaulting to today in UTC
`fromTimezone`	string	`America/New_York`	Source timezone identifier
`toTimezone`	string	`Europe/London`	Target timezone identifier
`timeDifference`	number	`5`	Time difference between zones
`fromOffset`	string	`-04:00`	The source timezone's UTC offset on that date, as +HH:MM or -HH:MM
`toOffset`	string	`+01:00`	The target timezone's UTC offset on that date, as +HH:MM or -HH:MM

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.

Status	What it means
`400` / `422`	The arguments did not validate. The message names the offending one.
`401`	The OAuth session is invalid or expired — reconnect the server.
`403`	Blocked by a key restriction or an IP allow-list. Never a bad identity.
`404`	This skill is not part of VerveKit. Check the catalog.
`429`	Out 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

Global Scheduling: Schedule international meetings by converting times across timezones
Calendar Apps: Display meeting times in user's local timezone automatically
Conference Planning: Coordinate multi-timezone events and conference calls
Travel Planning: Convert appointment times when traveling across timezones

Other ways to use Meeting Time Converter Skill

Set up Meeting Time Converter 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.

Call it as a REST APIOne HTTPS endpoint and an x-api-key header, with SDKs for Node, Python and .NET.APIVerve →Reference →

Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheets →Reference →

Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.VerveContext →Reference →