Dayze — Life Context

Update Event (calendar patch)

update_event

MUTATES one existing calendar event the authenticated user owns. Required: event_id (UUID). Optional patch (same fields as log_event): title, date / event_date, time / event_time, end_date, end_time, location, description (alias notes), category, external_url, image_url, timezone, visibility, people / with / person_ids, scoreboard (merged; null clears), reminder_enabled (false turns the push reminder off; needs a timed event to turn on), reminder_minutes_before. Adds a bedtime to a wake-only sleep: event_time (and event_date / end_date when it was the night before). Unknown or other-user event_id returns an error and does not create a row. For food-diary meals, prefer update_food (it syncs the mirrored event). Rebuilds life_state. Requires API key or OAuth with scope context. Share tokens cannot write. ($0.10; API key required)

Input Schema

Name	Required	Description
`date`	No	Alias for event_date.
`time`	No	Alias for event_time.
`with`	No	Alias for people.
`notes`	No	Alias for description.
`title`	No	Updated title (replaces). Cannot be empty.
`people`	No	People names or person UUIDs to add (event_people role=with). Does not remove existing tags.
`category`	No	e.g. sleep, funeral, family, work, travel. Stored as events.category and event_type.
`end_date`	No	Optional end date YYYY-MM-DD (multi-day, or a night that ends the next day).
`end_time`	No	Optional end time (same formats as event_time).
`event_id`	Yes	UUID of a calendar event the authenticated user owns
`location`	No	Empty or null clears
`timezone`	No	IANA timezone for wall-clock display. Empty or null clears.
`image_url`	No	Cover image URL. Empty or null clears.
`event_date`	No	Start date YYYY-MM-DD, YYYY-MM, or YYYY. Alias: date.
`event_time`	No	Start time: 8pm, 20:00, or 20:00:00. Empty or null clears. Alias: time.
`person_ids`	No	Owned person UUIDs to tag (user-scoped).
`request_id`	No	Client idempotency key (retries return original successful result).
`scoreboard`	No	Operating status as data (not description prose). state is required when the event has no scoreboard yet. On update_event fields merge; a null field clears it; scoreboard null removes the record.
`visibility`	No	Updates both events.visibility and the enforced events.is_private flag.
`description`	No	Notes about the event (replaces). Empty or null clears. Alias: notes.
`person_name`	No	One person to tag, by name.
`external_url`	No
`people_names`	No	Alias for people.
`date_precision`	No	Soft date precision stored in metadata.
`idempotency_key`	No	Alias for request_id.
`reminder_enabled`	No	Turn the push reminder on or off. A timed event is needed to turn it on; all-day events stay off.
`reminder_minutes_before`	No	Push lead time in minutes (snapped to 0, 5, 15, 30, 60, 1440 or 10080).

Output Schema

Name	Required	Description
`event`	Yes	A Dayze calendar event record.
`account`	No	The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
`changed`	Yes	Changed fields with before and after values.
`provenance`	No	Which connector wrote the record and which connected Dayze account received it.
`people_tagged`	Yes
`unresolved_people`	Yes
`life_state_rebuilt`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 21, 2026

addedInput schema / properties / reminder_enabled

Added value: +{
+  "description": "Turn the push reminder on or off. A timed event is needed to turn it on; all-day events stay off.",
+  "type": "boolean"
+}

addedInput schema / properties / reminder_minutes_before

Added value: +{
+  "description": "Push lead time in minutes (snapped to 0, 5, 15, 30, 60, 1440 or 10080).",
+  "type": "number"
+}

Changed2 schema fields changedOct 3, 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 / provenance

Added value: +{
+  "additionalProperties": false,
+  "description": "Which connector wrote the record and which connected Dayze account received it.",
+  "properties": {
+    "account": {
+      "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"
+    },
+    "channel": {
+      "description": "Always mcp_connector.",
+      "type": "string"
+    },
+    "connector": {
+      "additionalProperties": false,
+      "properties": {
+        "kind": {
+          "description": "oauth or api_key.",
+          "type": "string"
+        },
+        "name": {
+          "description": "The connected app or API-key label shown to the account owner.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "kind",
+        "name"
+      ],
+      "type": "object"
+    },
+    "source": {
+      "description": "chatgpt for ChatGPT OAuth writes; mcp for another OAuth app or API key.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "source",
+    "channel",
+    "connector",
+    "account"
+  ],
+  "type": "object"
+}

Changed8 schema fields changedSep 29, 2026

changedInput schema / properties / category / description

Previous value: -"e.g. funeral, family, work, travel. Stored as events.category and event_type."New value: +"e.g. sleep, funeral, family, work, travel. Stored as events.category and event_type."

changedInput schema / properties / description / description

Previous value: -"Empty or null clears"New value: +"Notes about the event (replaces). Empty or null clears. Alias: notes."

changedInput schema / properties / end_date / description

Previous value: -"Optional end date YYYY-MM-DD (all-day multi-day)."New value: +"Optional end date YYYY-MM-DD (multi-day, or a night that ends the next day)."

addedInput schema / properties / image_url

Added value: +{
+  "description": "Cover image URL. Empty or null clears.",
+  "type": "string"
+}

addedInput schema / properties / notes

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

addedInput schema / properties / people_names / description
```
Added value: +"Alias for people."
```
addedInput schema / properties / person_name / description
```
Added value: +"One person to tag, by name."
```

addedInput schema / properties / timezone

Added value: +{
+  "description": "IANA timezone for wall-clock display. Empty or null clears.",
+  "type": "string"
+}

Changed1 schema field changedSep 26, 2026

addedInput schema / properties / scoreboard

Added value: +{
+  "additionalProperties": false,
+  "description": "Operating status as data (not description prose). state is required when the event has no scoreboard yet. On update_event fields merge; a null field clears it; scoreboard null removes the record.",
+  "properties": {
+    "blocker": {
+      "type": "string"
+    },
+    "evidence": {
+      "type": "string"
+    },
+    "last_verified": {
+      "description": "YYYY-MM-DD",
+      "type": "string"
+    },
+    "metric": {
+      "description": "Progress readout, e.g. 2/5",
+      "type": "string"
+    },
+    "next_review": {
+      "description": "YYYY-MM-DD",
+      "type": "string"
+    },
+    "next_step": {
+      "type": "string"
+    },
+    "owner": {
+      "type": "string"
+    },
+    "state": {
+      "enum": [
+        "not_started",
+        "on_track",
+        "at_risk",
+        "blocked",
+        "done"
+      ],
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedSep 26, 2026

addedInput schema / properties / visibility

Added value: +{
+  "description": "Updates both events.visibility and the enforced events.is_private flag.",
+  "enum": [
+    "private",
+    "friends",
+    "public"
+  ],
+  "type": "string"
+}

Changed1 schema field changedSep 17, 2026

changedInput schema / properties / request_id / description

Previous value: -"Client idempotency key (retries return original result)."New value: +"Client idempotency key (retries return original successful result)."

Changed2 schema fields changedSep 13, 2026

addedInput schema / properties / date_precision

Added value: +{
+  "description": "Soft date precision stored in metadata.",
+  "enum": [
+    "day",
+    "month",
+    "year",
+    "approx"
+  ],
+  "type": "string"
+}

changedInput schema / properties / event_date / description

Previous value: -"Start date YYYY-MM-DD. Alias: date."New value: +"Start date YYYY-MM-DD, YYYY-MM, or YYYY. Alias: date."

Changed2 schema fields changedSep 4, 2026

addedInput schema / properties / idempotency_key

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

addedInput schema / properties / request_id

Added value: +{
+  "description": "Client idempotency key (retries return original result).",
+  "type": "string"
+}

Changed1 schema field changedAug 31, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "changed": {
+      "additionalProperties": true,
+      "description": "Changed fields with before and after values.",
+      "type": "object"
+    },
+    "event": {
+      "additionalProperties": true,
+      "description": "A Dayze calendar event record.",
+      "type": "object"
+    },
+    "life_state_rebuilt": {
+      "type": "boolean"
+    },
+    "people_tagged": {
+      "items": {
+        "additionalProperties": true,
+        "description": "A Dayze person or contact record.",
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "unresolved_people": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "event",
+    "changed",
+    "people_tagged",
+    "unresolved_people",
+    "life_state_rebuilt"
+  ],
+  "type": "object"
+}

AddedAug 31, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond annotations, it discloses error behavior for unknown or other-user event IDs, side effects such as rebuilding life_state, merge/null semantics for scoreboard, and reminder on/off constraints. Authentication and cost are also stated. The annotations declare readOnlyHint=false and destructiveHint=false, which is consistent with a patch operation that does not delete the event.

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?

The definition is front-loaded with the mutation and required parameter before listing optional fields and edge cases. It is dense and long, but the complexity of 27 parameters justifies most of the length; a few parenthetical details could be trimmed without loss.

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

Completeness5/5

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

Given a rich output schema, high schema coverage, and explicit annotations, the description supplies the remaining operational context: auth requirements, failure behavior, side effects, aliasing, and the relevant alternative tool. Nothing critical is missing for correct invocation.

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 96%, so the schema carries most parameter documentation. The description still adds meaningful patch semantics beyond the schema, including alias groups, scoreboard merge/null behavior, and the timed-event requirement for reminders. It does not cover every edge parameter, but the added context is substantial.

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

Purpose5/5

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

The description uses a specific verb and resource: 'MUTATES one existing calendar event the authenticated user owns.' It also distinguishes the tool from log_event (creation) and explicitly routes food-diary updates to update_food, so an agent can identify it without inspecting sibling schemas.

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

Usage Guidelines5/5

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

It states the core usage condition (existing event owned by the authenticated user), names event_id as required, and gives an explicit alternative for food-diary meals: use update_food. It also sets boundaries around authentication and share-token write access.

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

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.