Dayze — Life Context

Unlink People

unlink_people

Destructive

Preview first, 30-day undo. Remove a person↔person graph edge (by connection_id, or person_id + other_person_id). Reviewed and reversible: first call preview_destructive_change({ tool: "unlink_people", arguments: { connection_id } }), which stores the exact change without applying it. After the user confirms, call unlink_people 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
`person_id`	No
`preview_id`	Yes	preview_id returned by preview_destructive_change for this tool.
`request_id`	Yes	Required idempotency key; retries return the original receipt.
`connection_id`	No
`idempotency_key`	No	Alias for request_id.
`other_person_id`	No
`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
`unlinked`	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
`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"
+}

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

addedInput schema / required

Added value: +[
+  "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"
+}
```

AddedSep 4, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare destructiveHint=true, and the description adds substantial context beyond them: the mandatory preview step, the 30-day undo window via restore_change, the rule that an edited record cannot be restored, idempotency via request_id, and cost/auth requirements. This is exactly the kind of behavioral detail an agent needs for a destructive tool.

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 key constraint ('Preview first, 30-day undo'), then procedurally ordered details. It is dense and somewhat long, but every sentence carries actionable information with little redundancy.

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?

Despite an output schema existing, the description still notes the returned restore_id and how to use it. Combined with the preview/confirm/restore workflow, an agent has everything needed to call this correctly.

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 57%, but the description compensates by explaining the alternative identification paths (connection_id vs. person_id + other_person_id) and the roles of preview_id, restore_window_acknowledged, and request_id. It adds meaning beyond the raw schema property list.

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 first sentence names a specific verb+resource: 'Remove a person↔person graph edge,' and it disambiguates the target by giving the two accepted identifier forms. It is clearly distinct from the sibling link_people / update_people_link operations.

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 lays out a precise use procedure: preview first via preview_destructive_change, then call with preview_id after user confirmation. It does not explicitly name when to prefer this over siblings like update_people_link or delete_person, but the workflow context is unambiguous.

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.