Dayze — Life Context

Update Pending Reply

update_pending_reply

Pending Replies: change one reply by reply_id: its draft (replaces; null clears), summary, channel, category, received_at, person (person_id, or person_name linked only on one match), source, or status pending (reopen / unsnooze) or snoozed with snooze_until. Unknown or other-user reply_id returns not_found. To mark it sent or dismissed use resolve_pending_reply. Never sends anything. Requires API key or OAuth with context.write. ($0.10; API key required)

Input Schema

TableJSON Schema

Name	Required	Description
`draft`	No	The reply text to send later, max 20,000 characters. Replaces the saved draft; empty or null clears. Alias: draft_message.
`source`	No	The email the reply answers, as ids only (e.g. a search_gmail id is a message_id). Never a subject, sender or text. On update, null clears it.
`status`	No
`channel`	No	Where to reply: whatsapp, email, sms, call, imessage, telegram, instagram, facebook, signal, linkedin, twitter, slack, teams, work_email, zoom, dayze, other. Default email when source is set, else other.
`summary`	No	One line (max 280) in your own words: what the reply is about. Never paste the email body, subject line or sender address.
`category`	No
`reply_id`	Yes	From create_pending_reply or get_pending_replies.
`person_id`	No
`request_id`	No	Client idempotency key (retries return original result).
`person_name`	No
`received_at`	No
`snooze_until`	No	ISO date-time, with status snoozed.
`draft_message`	No	Alias for draft.
`idempotency_key`	No	Alias for request_id.

Output Schema

TableJSON Schema

Name	Required	Description
`reply`	Yes	One reply the user owes (Inbox → Pending Replies). Dayze never sends it.
`account`	No	The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
`message`	Yes
`provenance`	No	Which connector wrote the record and which connected Dayze account received it.
`person_link`	No	Whether a contact was linked. Linked only on one resolve_person match or an owned person_id.
`source_saved`	Yes
`changed_fields`	Yes
`life_state_rebuilt`	Yes

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

Changed3 schema fields changedOct 1, 2026

addedOutput schema / properties / reply / properties / is_private

Added value: +{
+  "description": "Always true.",
+  "type": "boolean"
+}

addedOutput schema / properties / reply / properties / visibility

Added value: +{
+  "description": "Always private: Pending Replies have no sharing setting.",
+  "type": "string"
+}

changedOutput schema / properties / reply / required

Previous value: -[
-  "reply_id",
-  "person_name",
-  "person_id",
-  "channel",
-  "category",
-  "summary",
-  "draft",
-  "status",
-  "state",
-  "due",
-  "received_at",
-  "source"
-]New value: +[
+  "reply_id",
+  "person_name",
+  "person_id",
+  "channel",
+  "category",
+  "summary",
+  "draft",
+  "status",
+  "state",
+  "due",
+  "received_at",
+  "source",
+  "visibility",
+  "is_private"
+]

Changed1 schema field changedSep 30, 2026

addedOutput schema / properties / reply / properties / approved_at

Added value: +{
+  "description": "PHI-427: when the owner approved the draft and opened it in Gmail, or null. Dayze never sends; the Gmail sync closes the reply when the email goes out.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed1 schema field changedSep 29, 2026
- addedInput schema / properties / draft_message
```
Added value: +{
+  "description": "Alias for draft.",
+  "type": "string"
+}
```

Changed2 schema fields changedSep 29, 2026

addedOutput schema / properties / reply / properties / due

Added value: +{
+  "description": "Owed now: pending, or snoozed with snooze_until passed. False while a snooze runs, and when sent or dismissed.",
+  "type": "boolean"
+}

changedOutput schema / properties / reply / required

Previous value: -[
-  "reply_id",
-  "person_name",
-  "person_id",
-  "channel",
-  "category",
-  "summary",
-  "draft",
-  "status",
-  "state",
-  "received_at",
-  "source"
-]New value: +[
+  "reply_id",
+  "person_name",
+  "person_id",
+  "channel",
+  "category",
+  "summary",
+  "draft",
+  "status",
+  "state",
+  "due",
+  "received_at",
+  "source"
+]

AddedSep 29, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false) by disclosing null-clears semantics, that unknown or other-user reply_id returns not_found, auth requirements (API key or OAuth with context.write), and cost ($0.10). These are exactly the operational facts an agent needs.

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 but front-loaded, with the resource and primary action stated first and the alternative/auth/cost clauses trailing. Nearly every clause carries information; the parenthetical field list is long but earns its place for a 14-parameter tool.

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 mutation tool with a nested source object and an output schema, the description supplies the missing pieces: field semantics, error behavior, auth, cost, and the sibling routing. Nothing an agent needs to call it correctly is absent.

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 64%, and the description adds real meaning: null clears the draft, person_name links only on a single match, status pending means reopen/unsnooze while snoozed requires snooze_until. It doesn't cover every parameter (e.g., request_id/idempotency, category) but the semantic additions exceed what the schema alone conveys.

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 (change/update) on a specific resource (one pending reply identified by reply_id) and enumerates the mutable fields. It explicitly differentiates itself from resolve_pending_reply, so an agent can route without opening either 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?

Explicitly names the alternative and the condition selecting it: 'To mark it sent or dismissed use resolve_pending_reply.' It also states the negative scope ('Never sends anything') and the reopen/unsnooze semantics for status, leaving no inference needed.

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.