Dayze — Life Context

Archive Inventory Item

archive_inventory_item

Destructive

Preview first, 30-day undo. Archive an inventory item instead of deleting it (status archived, archived_at set; valuations, people links and photos are kept). Reviewed and reversible: first call preview_destructive_change({ tool: "archive_inventory_item", arguments: { inventory_id } }), which stores the exact change without applying it. After the user confirms, call archive_inventory_item with preview_id, restore_window_acknowledged: true and request_id; the reviewed preview is applied exactly and a changed record is refused. Returns restore_id; restore_change({ restore_id }) undoes it for 30 days unless the record was edited since. ($0.10; API key required)

Input Schema

TableJSON Schema

Name	Required	Description
`reason`	No	Why it is archived (kept on the receipt).
`preview_id`	Yes	preview_id returned by preview_destructive_change for this tool.
`request_id`	Yes	Required idempotency key; retries return the original receipt.
`inventory_id`	Yes	The item id from add_inventory_item, get_inventory or search_inventory.
`idempotency_key`	No	Alias for request_id.
`restore_window_acknowledged`	Yes	Must be true after reviewing the preview and its 30-day restore window.

Output Schema

TableJSON Schema

Name	Required	Description
`account`	No	The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
`message`	No
`archived`	No
`preview_id`	No
`provenance`	No	Which connector wrote the record and which connected Dayze account received it.
`restore_id`	No	Pass to restore_change to undo within restore_window_days.
`reversible`	No
`inventory_id`	No
`idempotent_replay`	No
`restore_expires_at`	No
`restore_window_days`	No

Schema Changelog

Changes observed during successful MCP inspections.

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

Changed2 schema fields changedSep 29, 2026
- addedInput schema / properties / inventory_id / description
```
Added value: +"The item id from add_inventory_item, get_inventory or search_inventory."
```
- addedInput schema / properties / reason / description
```
Added value: +"Why it is archived (kept on the receipt)."
```

Changed10 schema fields changedSep 27, 2026

addedInput schema / properties / preview_id

Added value: +{
+  "description": "preview_id returned by preview_destructive_change for this tool.",
+  "type": "string"
+}

changedInput schema / properties / request_id / description

Previous value: -"Client idempotency key (retries return original result)."New value: +"Required idempotency key; retries return the original receipt."

addedInput schema / properties / restore_window_acknowledged

Added value: +{
+  "description": "Must be true after reviewing the preview and its 30-day restore window.",
+  "type": "boolean"
+}

changedInput schema / required

Previous value: -[
-  "inventory_id"
-]New value: +[
+  "inventory_id",
+  "preview_id",
+  "restore_window_acknowledged",
+  "request_id"
+]

addedOutput schema / properties / idempotent_replay
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / preview_id
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / restore_expires_at
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / restore_id

Added value: +{
+  "description": "Pass to restore_change to undo within restore_window_days.",
+  "type": "string"
+}

addedOutput schema / properties / restore_window_days
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / reversible
```
Added value: +{
+  "type": "boolean"
+}
```

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

AddedSep 1, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations declare destructiveHint=true, and the description goes well beyond that: it discloses what is preserved (valuations, people links, photos), the 30-day restore window, that a changed record is refused, idempotency behavior on retries, and that a preview_id is mandatory. It also notes auth (API key) and cost ($0.10), which 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-loaded with the two most important facts ('Preview first, 30-day undo'), then the mechanism and parameters. Dense but every clause carries operational meaning; the parenthetical cost/auth note is compact rather than wasteful.

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 destructive, multi-parameter, preview-gated mutation with an output schema present, the description covers the prerequisites, the reversibility contract, the failure case (edited record refused), and the undo path. Nothing an agent needs to call it safely is missing.

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 100%, so the baseline is 3, but the description adds cross-parameter meaning the schema cannot: preview_id must originate from preview_destructive_change invoked for this exact tool, restore_window_acknowledged must be true after reviewing, and request_id is the idempotency key. The return of restore_id is also tied back to restore_change.

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+resource (archive an inventory item) and immediately distinguishes it from deletion by naming the resulting state (status archived, archived_at set). The resource qualifier separates it cleanly from the sibling archive_asset, archive_event, archive_expense, and archive_trip tools.

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?

Gives the full ordered workflow: call preview_destructive_change first, wait for user confirmation, then call this tool with preview_id, restore_window_acknowledged and request_id. It also names the alternative (restore_change) and the exact condition under which undo applies, leaving nothing to inference.

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.