Dayze — Life Context

Resolve Pending Reply

resolve_pending_reply

Pending Replies: mark a reply done: sent (default; the user replied, logged privately in the contact's history) or dismissed. Dayze sends nothing. By reply_id, or person_name / person_id when that person has exactly one unsent reply (otherwise the candidates come back and nothing changes). Marking sent writes one private interaction for the linked contact (not for an unlinked reply, and not twice); interaction in the result says what was written. Reopen with update_pending_reply status pending. Requires API key or OAuth with context.write. ($0.05; API key required)

Input Schema

TableJSON Schema

Name	Required	Description
`outcome`	No
`reply_id`	No
`person_id`	No
`request_id`	No	Client idempotency key (retries return original result).
`person_name`	No
`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
`outcome`	Yes	sent or dismissed
`resolved`	Yes	True when this call changed the reply.
`provenance`	No	Which connector wrote the record and which connected Dayze account received it.
`interaction`	No	The contact-history write-back of a reply marked sent by this call; null when nothing was marked sent now.
`already_resolved`	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"
+]

Changed2 schema fields changedSep 30, 2026

addedOutput schema / properties / interaction

Added value: +{
+  "additionalProperties": false,
+  "description": "The contact-history write-back of a reply marked sent by this call; null when nothing was marked sent now.",
+  "properties": {
+    "interaction_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "logged": {
+      "description": "True when this call wrote it.",
+      "type": "boolean"
+    },
+    "occurred_at": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "person_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "reason": {
+      "description": "logged, unlinked, already_logged, gmail_sync_logged or storage_error",
+      "type": "string"
+    },
+    "summary": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "visibility": {
+      "description": "Always private: interactions are the owner's alone.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "logged",
+    "reason",
+    "interaction_id",
+    "person_id",
+    "visibility"
+  ],
+  "type": [
+    "object",
+    "null"
+  ]
+}

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

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?

Adds substantial context beyond the annotations: Dayze sends nothing, marking sent writes one private interaction for the linked contact (not for unlinked replies, not twice), the result reports the interaction, reopening is possible, and it requires API key or OAuth with context.write plus a $0.05 cost. Annotations only say write/non-destructive/non-open-world.

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, leading with the action and outcomes before the lookup rules and side effects. Parenthetical clauses are information-bearing rather than filler, though the single long paragraph could be broken up for easier scanning.

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?

An output schema exists, so return values need no explanation, and the description still covers side effects, auth, cost, and failure behavior. Nothing an agent needs to invoke this correctly 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?

With only 33% schema coverage, the description compensates well: it defines the outcome enum semantics (sent default vs dismissed), the meaning of reply_id, and the conditional constraint on person_name/person_id. request_id/idempotency_key are left to the schema, which already documents them.

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 (mark done) on a specific resource (pending reply), with the two outcomes named explicitly. It clearly distinguishes itself from siblings create_pending_reply, get_pending_replies, and update_pending_reply.

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 explicit selection rules: use reply_id, or person_name/person_id only when that person has exactly one unsent reply, otherwise candidates are returned and nothing changes. It also names update_pending_reply as the way to reopen, so the agent knows both the when and the when-not.

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.