Dayze — Life Context

Merge People

merge_people

Destructive

Apply a reviewed durable preview atomically; undo_contact_change accepts restore_id for 30 days if unchanged. Fold duplicate CRM contact(s) into primary_person_id (same human, spelling variants). Prefer score_people_duplicates first. Not for “X knows Y” — use link_people for relationships. ($0.10; API key required)

Input Schema

TableJSON Schema

Name	Required	Description
`preview_id`	Yes	Durable preview_id returned by merge_people_preview; review the 30-day restore window before applying.
`request_id`	No	Client idempotency key (retries return original result).
`idempotency_key`	No	Alias for request_id.
`primary_person_id`	Yes
`duplicate_person_ids`	Yes
`restore_window_acknowledged`	Yes	Must be true — confirms the 30-day restore window was reviewed before apply.

Output Schema

TableJSON Schema

Name	Required	Description
`person`	No	CRM person record.
`account`	No	The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
`message`	No
`provenance`	No	Which connector wrote the record and which connected Dayze account received it.
`restore_id`	No
`reversible`	No
`merged_person_ids`	No
`restore_expires_at`	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"
+}

Changed6 schema fields changedSep 16, 2026

addedInput schema / properties / preview_id

Added value: +{
+  "description": "Durable preview_id returned by merge_people_preview; review the 30-day restore window before applying.",
+  "type": "string"
+}

addedInput schema / properties / restore_window_acknowledged

Added value: +{
+  "description": "Must be true — confirms the 30-day restore window was reviewed before apply.",
+  "type": "boolean"
+}

changedInput schema / required

Previous value: -[
-  "primary_person_id",
-  "duplicate_person_ids"
-]New value: +[
+  "primary_person_id",
+  "duplicate_person_ids",
+  "preview_id",
+  "restore_window_acknowledged"
+]

addedOutput schema / properties / restore_expires_at
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / restore_id
```
Added value: +{
+  "type": "string"
+}
```
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 already mark it destructive, but the description adds substantial context beyond them: atomic application, the undo path via undo_contact_change with restore_id valid for 30 days if unchanged, the cost ($0.10), and the auth requirement (API key). These are genuinely useful behavioral traits not present in the 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?

Dense and mostly front-loaded, with prerequisite and alternative routing clearly stated. The opening clause about atomic apply and undo is slightly awkward as a lead-in, but every sentence carries useful information.

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, atomic merge with a required preview and a 30-day restore window, the description covers reversibility, prerequisites, alternatives, cost, and auth. An output schema exists, so return-value documentation is correctly omitted.

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 67%, and the description adds meaning beyond it by framing primary_person_id as the fold target and duplicate_person_ids as the 'same human, spelling variants' set, plus tying the preview/restore window to the workflow. It clarifies the two undocumented required parameters but does not detail idempotency behavior.

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: 'Fold duplicate CRM contact(s) into primary_person_id (same human, spelling variants).' It also distinguishes itself from siblings by explicitly excluding the relationship case ('Not for "X knows Y" — use link_people'). An agent can identify this as the duplicate-contact merge tool without opening the schema.

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?

Names both the prerequisite workflow ('Prefer score_people_duplicates first', 'Apply a reviewed durable preview') and the contrasting alternative (link_people for relationships). It clearly communicates when to use this tool and when not to.

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.