Overview
The API treats `time` as a wall-clock time in `fromTimezone` on `date`. It first reads the date and time as if they were UTC, then looks up the UTC offset of each zone for that moment using the runtime's IANA timezone data. Subtracting the source offset gives the real instant, which is then formatted in `toTimezone` as `convertedTime` in 24-hour `HH:MM:SS` form.
`date` is optional and defaults to today's date in UTC. It matters because offsets follow daylight saving rules: on a summer date `America/New_York` reports `-04:00` and on a winter date `-05:00`. `fromOffset` and `toOffset` are those offsets as `+HH:MM` or `-HH:MM`, and `timeDifference` is the target offset minus the source offset in hours, so it can be fractional for zones such as `Asia/Kolkata` (+5.5) and negative when the target is behind.
`convertedTime` carries no date, so a conversion that crosses midnight does not say whether the result falls on the previous or next day; compare `timeDifference` with the input time to work that out. Each timezone is validated on its own, and a name the runtime does not recognise returns a 400 that says which parameter was wrong. A date and time that do not form a valid moment also return a 400. Offsets are looked up at the input reading as UTC, so within a few hours of a daylight saving change the result can be off by an hour.
Live Test Meeting Time Conversion for AI Agents Source →
The tool
Once your client is connected to the VerveContext server, this appears in its tool list as MeetingTimeConversionforAIAgents. 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": "MeetingTimeConversionforAIAgents",
"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 source covers is enough for it to reach for MeetingTimeConversionforAIAgents 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"
}
}
}https://api.vervecontext.com/v1/mcpPer-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 |
|---|---|---|
timeRequired | string | Time in HH:MM or HH:MM:SS format (24-hour) time |
fromTimezoneRequired | string | Source timezone: an IANA name (America/New_York), a North American abbreviation (EST, EDT, PST, PDT and so on, always DST-aware) or a UTC/GMT offset such as UTC+05:30 timezone |
toTimezoneRequired | string | Target timezone, in the same forms as fromTimezone timezone |
dateOptional | 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.
{
"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 |
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 originalTime: 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.
| 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 source is not part of VerveContext. Check the catalog. |
429 | Out of credits, or a brief rate limit. The message tells them apart. |
A call costs 1 credit 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 Conversion for AI Agents
Set up Meeting Time Conversion 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.
Related
More in Data Conversion: