Reference data & utilities
These helper tools support the others: one grounds the session in the right timezone and identity, the other turns human-friendly date phrases into concrete ranges. Master-data enumeration (categoriesCategoryA visual indicator (a color) applied to appointments to classify or label them., time markersTime markerA visual indicator on an appointment, separate from its category, used to flag a status or condition at a point in time.) is exposed as data sources, not tools, so read dimescheduler://categories or dimescheduler://time-markers instead of calling a tool.
Get session context
Tool: get_session_context
Returns the grounding facts for the current MCP serverMCP serverThe Model Context Protocol endpoint that exposes scheduling operations as tools to AI assistants. It is authenticated with API keys and translates tool calls into Dime.Scheduler API calls. session: the server time in UTC and in local time, the effective IANA timezone, and the identity of the current user and organization. Call it once at the start of a conversation. From then on the assistant knows what "today" is in the user's timezone and can omit the timeZone parameter on later tool calls, because the server applies the same fallback chain (the user's profile timezone, then the organization default).
The tool takes no parameters. The response contains:
| Field | Description |
|---|---|
server_now_utc | Current server time in UTC |
server_now_local | Current server time in the effective timezone, e.g. 2026-05-21 16:32 (Europe/Brussels); the UTC form when no timezone is set |
effective_timezone | Resolved IANA timezone: the user's profile timezone, otherwise the organization default, otherwise null |
user | email, display_name, and profile_timezone of the current user |
organization | id, name, and default_timezone of the organization |
When effective_timezone is null, no timezone is set anywhere: ask the user for one, or have an administrator configure an organization default.
Example prompt
"What time is it for me right now, and which timezone are we working in?"
Parse relative time
Tool: parse_relative_time
Converts a natural-language relative time expression ("this week", "5 days ago", "in 3 months") into concrete UTC and local-time ranges. Use this before calling tools that take an explicit startDateTime / endDateTime whenever the user phrases a date relatively.
| Parameter | Type | Required | Description |
|---|---|---|---|
expression | string | Yes | Natural-language expression to parse (e.g. this week, next month, 5 days ago) |
timeZone | string | Yes | IANA timezone identifier |
referenceTime | string | No | Reference time in ISO 8601 (defaults to the current time in the specified time zone) |
Supported expressions
this week,next week,last week(Monday → Sunday)this month,next month,last monththis year,next year,last yeartoday,tomorrow,yesterday- Numeric offsets:
5 days ago,2 weeks from now,in 3 months, …
The parser uses Monday as the first day of the week, regardless of locale. If your assistant is built for a Sunday-start locale, account for the off-by-one.
Example prompt
"Parse 'next week' in Europe/Brussels timezone."