Dayze — Life Context

Preview Destructive Change

preview_destructive_change

Review a destructive change before it happens. Stores the exact rows delete_food, delete_place, delete_place_visit, archive_inventory_item, archive_asset, reset_tracker, unlink_people, remove_person_alias, convert_contact_entity, bulk_dismiss_clarifications, delete_memory, delete_moment, merge_moments, merge_memory, correct_memory_atom would delete, archive or overwrite (with their before-state and linked records) without changing anything, and returns preview_id, operations, expires_at (30 minutes) and restore_window_days (30). Show it to the user, then call the named tool with preview_id, restore_window_acknowledged: true and request_id. ($0.05; API key required)

Input Schema

TableJSON Schema

Name	Required	Description
`tool`	Yes
`arguments`	Yes	The arguments you would pass to that tool (e.g. { food_id }).
`request_id`	No	Client idempotency key (retries return original result).
`idempotency_key`	No	Alias for request_id.

Output Schema

TableJSON Schema

Name	Required	Description
`tool`	Yes
`account`	No	The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
`summary`	No
`next_step`	No
`target_id`	No
`expires_at`	No
`operations`	No
`preview_id`	Yes
`provenance`	No	Which connector wrote the record and which connected Dayze account received it.
`reversible`	Yes
`nothing_to_change`	No
`restore_window_days`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 3, 2026

changedInput schema / properties / tool / enum

Previous value: -[
-  "delete_food",
-  "delete_place",
-  "delete_place_visit",
-  "archive_inventory_item",
-  "archive_asset",
-  "reset_tracker",
-  "unlink_people",
-  "remove_person_alias",
-  "convert_contact_entity",
-  "bulk_dismiss_clarifications",
-  "delete_memory",
-  "merge_memory",
-  "correct_memory_atom"
-]New value: +[
+  "delete_food",
+  "delete_place",
+  "delete_place_visit",
+  "archive_inventory_item",
+  "archive_asset",
+  "reset_tracker",
+  "unlink_people",
+  "remove_person_alias",
+  "convert_contact_entity",
+  "bulk_dismiss_clarifications",
+  "delete_memory",
+  "delete_moment",
+  "merge_moments",
+  "merge_memory",
+  "correct_memory_atom"
+]

Changed1 schema field changedOct 3, 2026

changedInput schema / properties / tool / enum

Previous value: -[
-  "delete_food",
-  "delete_place",
-  "delete_place_visit",
-  "archive_inventory_item",
-  "archive_asset",
-  "reset_tracker",
-  "unlink_people",
-  "remove_person_alias",
-  "convert_contact_entity",
-  "bulk_dismiss_clarifications",
-  "delete_memory"
-]New value: +[
+  "delete_food",
+  "delete_place",
+  "delete_place_visit",
+  "archive_inventory_item",
+  "archive_asset",
+  "reset_tracker",
+  "unlink_people",
+  "remove_person_alias",
+  "convert_contact_entity",
+  "bulk_dismiss_clarifications",
+  "delete_memory",
+  "merge_memory",
+  "correct_memory_atom"
+]

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"
+}

Changed1 schema field changedSep 30, 2026

changedInput schema / properties / tool / enum

Previous value: -[
-  "delete_food",
-  "delete_place",
-  "delete_place_visit",
-  "archive_inventory_item",
-  "archive_asset",
-  "reset_tracker",
-  "unlink_people",
-  "remove_person_alias",
-  "convert_contact_entity",
-  "bulk_dismiss_clarifications"
-]New value: +[
+  "delete_food",
+  "delete_place",
+  "delete_place_visit",
+  "archive_inventory_item",
+  "archive_asset",
+  "reset_tracker",
+  "unlink_people",
+  "remove_person_alias",
+  "convert_contact_entity",
+  "bulk_dismiss_clarifications",
+  "delete_memory"
+]

Changed1 schema field changedSep 27, 2026

changedInput schema / properties / tool / enum

Previous value: -[
-  "delete_food",
-  "delete_place",
-  "archive_inventory_item",
-  "archive_asset",
-  "reset_tracker",
-  "unlink_people",
-  "remove_person_alias",
-  "convert_contact_entity",
-  "bulk_dismiss_clarifications"
-]New value: +[
+  "delete_food",
+  "delete_place",
+  "delete_place_visit",
+  "archive_inventory_item",
+  "archive_asset",
+  "reset_tracker",
+  "unlink_people",
+  "remove_person_alias",
+  "convert_contact_entity",
+  "bulk_dismiss_clarifications"
+]

AddedSep 27, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only supply the safety profile (destructiveHint=false, openWorldHint=false); the description adds substantial context beyond them: it captures before-state and linked records, states it changes nothing, discloses the 30-minute preview expiry, the 30-day restore window, the $0.05 cost, and the API-key requirement. This is exactly the behavioral detail the annotations cannot convey.

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-loads the purpose in the opening sentence and the workflow follows logically. The one weakness is that it re-lists all 15 destructive tools, duplicating the enum already present in the schema, which adds length that is not strictly earned.

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?

For a tool with nested objects, an enum, and an output schema (so return values need not be re-explained), the definition still covers the full preview-then-execute lifecycle, expiry, restore window, cost, and auth. An agent has everything needed to call it correctly.

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

Parameters3/5

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

Schema coverage is 75% and the schema already documents the arguments object ('the arguments you would pass to that tool') and request_id as an idempotency key. The description reiterates the tool/arguments relationship and the follow-up call's params (preview_id, restore_window_acknowledged), but that guidance mostly concerns the downstream destructive tool, so this stays at the baseline for a well-covered schema.

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?

States a specific verb and resource ('Review a destructive change before it happens') and immediately scopes the tool by enumerating the 15 mutating operations it covers. An agent can distinguish this preview from the actual destructive siblings without opening a schema.

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

Usage Guidelines4/5

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

It gives a clear workflow: preview first, 'Show it to the user, then call the named tool with preview_id, restore_window_acknowledged: true and request_id.' That is strong prescriptive guidance, but it names no when-not conditions and does not address when to prefer this generic preview over dedicated siblings like delete_moment_preview or delete_person_preview.

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.

Preview Destructive Change

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources