Dayze — Life Context

Calendar Events

get_events

Read-only

Authenticated user's calendar events. Prefer explicit from/to (YYYY-MM-DD). Shortcuts: today|week|month|year (calendar year)|decade. Browsing noise excluded by default. Records carry inspect_url (their Dayze page): cite with it, never build a link from an id; a record without one has no page (inspect_note says which). ($0.10; API key required)

Input Schema

TableJSON Schema

Name	Required	Description
`at`	No	ISO date-time to answer as of (default now), e.g. 2026-09-26T09:00:00+08:00.
`to`	No	Inclusive YYYY-MM-DD
`from`	No	Inclusive YYYY-MM-DD (preferred over range)
`kinds`	No	Filter by event_kind: life_event, calendar_block, todo, goal, travel_segment, food_log, health_record, transaction, media_log, work, family, personal. Alias "food" (also meal/drink/snack) matches the displayed Food category: food_log rows plus Meal/Drink/Snack life_events. total/has_more count only matching rows.
`limit`	No
`query`	No	Literal substring in title, description or location.
`range`	No
`cursor`	No
`offset`	No	Skip this many matching rows of a new snapshot (a cursor carries its own).
`date_to`	No	Alias for to.
`timezone`	No	IANA time zone for today (default: where the user is now, else their home zone).
`date_from`	No	Alias for from.
`redact_pii`	No	true: redact contact details, card and account numbers and secrets in description, location and scoreboard, even where this connection may see them. Never unredacts: without travel_secrets:read they are always redacted.
`event_kinds`	No	Alias for kinds.
`include_archived`	No
`include_browsing`	No	Include extension "Browsed domain · Xm" auto-events (default false)
`include_calendar_blocks`	No	Include Focus Time / calendar_block rows (default false)

Output Schema

TableJSON Schema

Name	Required	Description
`to`	Yes	Inclusive YYYY-MM-DD upper bound; null for all records.
`cap`	Yes
`from`	Yes	Inclusive YYYY-MM-DD lower bound; null for all records.
`range`	Yes
`total`	No
`events`	Yes
`account`	No	The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
`has_more`	No
`ordering`	No
`timezone`	Yes	Resolved timezone used for this event window and as fallback for rows without one.
`truncated`	Yes
`expires_at`	No
`next_cursor`	No
`server_time`	No
`snapshot_at`	No
`snapshot_id`	No
`inspect_note`	No	How to cite: link each record with its inspect_url, never a link built from an id; which record types here have no Dayze page.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 1, 2026

addedInput schema / properties / date_from

Added value: +{
+  "description": "Alias for from.",
+  "type": "string"
+}

addedInput schema / properties / date_to

Added value: +{
+  "description": "Alias for to.",
+  "type": "string"
+}

addedInput schema / properties / query

Added value: +{
+  "description": "Literal substring in title, description or location.",
+  "maxLength": 300,
+  "type": "string"
+}

Changed3 schema fields changedSep 30, 2026

addedInput schema / properties / event_kinds

Added value: +{
+  "description": "Alias for kinds.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / offset

Added value: +{
+  "description": "Skip this many matching rows of a new snapshot (a cursor carries its own).",
+  "type": "number"
+}

addedInput schema / properties / redact_pii

Added value: +{
+  "description": "true: redact contact details, card and account numbers and secrets in description, location and scoreboard, even where this connection may see them. Never unredacts: without travel_secrets:read they are always redacted.",
+  "type": "boolean"
+}

Changed2 schema fields changedSep 30, 2026

addedInput schema / properties / at

Added value: +{
+  "description": "ISO date-time to answer as of (default now), e.g. 2026-09-26T09:00:00+08:00.",
+  "type": "string"
+}

addedInput schema / properties / timezone

Added value: +{
+  "description": "IANA time zone for today (default: where the user is now, else their home zone).",
+  "type": "string"
+}

Changed2 schema fields changedSep 29, 2026

addedOutput schema / properties / account

Added value: +{
+  "additionalProperties": false,
+  "description": "The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.",
+  "properties": {
+    "display_name": {
+      "description": "Account display name.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "handle": {
+      "description": "Account handle, e.g. @goh.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "note": {
+      "description": "How to disclose the account to the user.",
+      "type": "string"
+    },
+    "qa_fixture": {
+      "description": "True for a known QA test account: its records are fixture data, not a real life.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "handle",
+    "display_name",
+    "qa_fixture",
+    "note"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / inspect_note

Added value: +{
+  "description": "How to cite: link each record with its inspect_url, never a link built from an id; which record types here have no Dayze page.",
+  "type": "string"
+}

Changed2 schema fields changedSep 26, 2026

addedOutput schema / properties / timezone

Added value: +{
+  "description": "Resolved timezone used for this event window and as fallback for rows without one.",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "events",
-  "range",
-  "from",
-  "to",
-  "cap",
-  "truncated"
-]New value: +[
+  "events",
+  "timezone",
+  "range",
+  "from",
+  "to",
+  "cap",
+  "truncated"
+]

Changed1 schema field changedSep 26, 2026

changedInput schema / properties / kinds / description

Previous value: -"Filter event_kind e.g. [\"life_event\",\"todo\"]"New value: +"Filter by event_kind: life_event, calendar_block, todo, goal, travel_segment, food_log, health_record, transaction, media_log, work, family, personal. Alias \"food\" (also meal/drink/snack) matches the displayed Food category: food_log rows plus Meal/Drink/Snack life_events. total/has_more count only matching rows."

Changed15 schema fields changedSep 16, 2026

addedInput schema / properties / cursor
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / include_archived
```
Added value: +{
+  "type": "boolean"
+}
```

addedInput schema / properties / limit

Added value: +{
+  "maximum": 500,
+  "minimum": 1,
+  "type": "number"
+}

changedInput schema / properties / range / enum

Previous value: -[
-  "today",
-  "week",
-  "month",
-  "year",
-  "decade"
-]New value: +[
+  "today",
+  "week",
+  "month",
+  "year",
+  "decade",
+  "all"
+]

addedOutput schema / properties / expires_at
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / from / description

Previous value: -"Inclusive YYYY-MM-DD lower bound."New value: +"Inclusive YYYY-MM-DD lower bound; null for all records."

changedOutput schema / properties / from / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

addedOutput schema / properties / has_more
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / next_cursor

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / ordering
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / server_time
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / snapshot_at
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / snapshot_id
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / to / description

Previous value: -"Inclusive YYYY-MM-DD upper bound."New value: +"Inclusive YYYY-MM-DD upper bound; null for all records."

changedOutput schema / properties / to / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

Changed2 schema fields changedSep 4, 2026

addedInput schema / properties / include_calendar_blocks

Added value: +{
+  "description": "Include Focus Time / calendar_block rows (default false)",
+  "type": "boolean"
+}

addedInput schema / properties / kinds

Added value: +{
+  "description": "Filter event_kind e.g. [\"life_event\",\"todo\"]",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed2 schema fields changedSep 1, 2026

addedInput schema / properties / from

Added value: +{
+  "description": "Inclusive YYYY-MM-DD (preferred over range)",
+  "type": "string"
+}

addedInput schema / properties / to

Added value: +{
+  "description": "Inclusive YYYY-MM-DD",
+  "type": "string"
+}

Changed1 schema field changedAug 31, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "cap": {
+      "type": "number"
+    },
+    "events": {
+      "items": {
+        "additionalProperties": true,
+        "description": "A Dayze calendar event record.",
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "from": {
+      "description": "Inclusive YYYY-MM-DD lower bound.",
+      "type": "string"
+    },
+    "range": {
+      "type": "string"
+    },
+    "to": {
+      "description": "Inclusive YYYY-MM-DD upper bound.",
+      "type": "string"
+    },
+    "total": {
+      "type": "number"
+    },
+    "truncated": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "events",
+    "range",
+    "from",
+    "to",
+    "cap",
+    "truncated"
+  ],
+  "type": "object"
+}

Changed1 schema field changedAug 27, 2026

addedInput schema / properties / include_browsing

Added value: +{
+  "description": "Include extension \"Browsed domain · Xm\" auto-events (default false)",
+  "type": "boolean"
+}

First observedJul 11, 2026

TDQS

A4/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the readOnly/openWorld annotations: it discloses a $0.10 cost and API-key requirement, that browsing auto-events are excluded by default, and a citation contract (records carry inspect_url, cite with it, never synthesize a link from an id; a record lacking one has no page and inspect_note says which). That is materially useful behavior an agent cannot infer from structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the resource, then range guidance, then the output citation rule, then cost/auth. Dense and parenthetical-heavy, but nearly every clause carries information; only the citation policy sentence is long enough to slow scanning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 17 params, an output schema, and rich annotations, the description covers the gaps that matter: cost, auth, default filtering, date-shortcut semantics, and how to handle returned inspect_url values. Pagination behavior (cursor vs offset snapshot) is left entirely to the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 76% and the description supplements it: from/to preferred over range, the today|week|month|year|decade shortcut vocabulary, and the default exclusion of browsing noise (include_browsing). It does not add meaning for limit, cursor, offset, include_archived, or query, which the schema already covers.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific resource and scope: "Authenticated user's calendar events." An agent can tell it apart from get_interactions, get_sleep, or get_transactions without opening a schema, though the retrieval verb itself is implied rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Prefer explicit from/to" and the shortcut list give parameter-level guidance, and default exclusions hint at scope, but the description never says when to reach for this tool over siblings such as search, get_life_context, or get_context_pack. Usage is implied rather than routed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Dayze — Life Context tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.