PrimeCal Context Snapshot v2
primecal_context_snapshot_v2 builds a bounded snapshot for AI agents without inlining oversized legacy event payloads.
Request Parameters
| Field | Type | Required | Notes |
|---|---|---|---|
verbosity | string | No | compact or full. Default compact. |
days | number | No | Default 14, min 1, max 30. |
tasksLimit | number | No | Default 25, max 200. |
eventsLimit | number | No | Default 40, max 100. |
includeCompletedTasks | boolean | No | Default false. |
calendarIds | number[] | No | Optional subset of accessible calendars. |
userTimezone | string | No | Optional logical timezone override for event rendering. |
Compact vs Full
Compact mode:
- Uses bounded event fields only
- Omits full descriptions and attendee lists
- Returns event pagination metadata separately in
eventsMeta - Is the recommended default for 14-day snapshots
Full mode:
- Allows richer event detail such as descriptions
- Still keeps the same outer structure
- Should be used only when the agent truly needs heavier event context
Response Structure
{
"generatedAt": "2026-06-09T09:00:00.000Z",
"verbosity": "compact",
"window": {
"days": 14,
"from": "2026-06-09T09:00:00.000Z",
"to": "2026-06-23T09:00:00.000Z",
"timezone": "Europe/Budapest"
},
"profile": {},
"calendars": [],
"tasks": [],
"upcomingEvents": [],
"eventsMeta": {
"totalCount": 12,
"truncated": false,
"nextCursor": null,
"timezone": "Europe/Budapest"
},
"summary": {
"calendarCount": 1,
"taskCount": 5,
"eventCount": 12,
"totalEventCount": 12
}
}
Usage Guidance
- Prefer
verbosity: "compact"for agent warm-up and periodic refresh. - Use
calendarIdsto scope large tenants down to the exact calendars an agent needs. - If more event detail is needed, follow the snapshot with targeted
primecal_calendars_events_get_v2calls.