Skip to main content
Glama

Dayze — Life Context

by com.dayze
OverviewDiscussionsAdmin

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

NameRequiredDescriptionDefault
draftNoThe reply text to send later, max 20,000 characters. Replaces the saved draft; empty or null clears. Alias: draft_message.
sourceNoThe 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.
statusNo
channelNoWhere to reply: whatsapp, email, sms, call, imessage, telegram, instagram, facebook, signal, linkedin, twitter, slack, reddit, teams, work_email, zoom, dayze, other; the platform the conversation is on (a Reddit thread is reddit, an Instagram group instagram). Default email when source is set, else other.
summaryNoOne line (max 280) in your own words: what the reply is about. Never paste the email body, subject line or sender address.
categoryNo
reply_idYesFrom create_pending_reply or get_pending_replies.
person_idNo
request_idNoClient idempotency key (retries return original result).
person_nameNo
received_atNo
snooze_untilNoISO date-time, with status snoozed.
draft_messageNoAlias for draft.
idempotency_keyNoAlias for request_id.

Output Schema

NameRequiredDescriptionDefault
replyYesOne reply the user owes (Inbox → Pending Replies). Dayze never sends it.
accountNoThe Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
messageYes
provenanceNoWhich connector wrote the record and which connected Dayze account received it.
person_linkNoWhether a contact was linked. Linked only on one resolve_person match or an owned person_id.
source_savedYes
changed_fieldsYes
life_state_rebuiltYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / channel / description
      Previous value: -"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."New value: +"Where to reply: whatsapp, email, sms, call, imessage, telegram, instagram, facebook, signal, linkedin, twitter, slack, reddit, teams, work_email, zoom, dayze, other; the platform the conversation is on (a Reddit thread is reddit, an Instagram group instagram). Default email when source is set, else other."
  2. Changed2 schema fields changed
    • 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"
+}
  3. Changed3 schema fields changed
    • 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"
+]
  4. Changed1 schema field changed
    • 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"
+  ]
+}
  5. Changed1 schema field changed
    • addedInput schema / properties / draft_message
      Added value: +{
+  "description": "Alias for draft.",
+  "type": "string"
+}
  6. Changed2 schema fields changed
    • 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"
+]
  7. Added

TDQS

A4.7/5.0
Behavior4/5

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

Adds context beyond annotations: 'Never sends anything' clarifies the non-destructive edit behavior even though destructiveHint=false, and 'Unknown or other-user reply_id returns not_found' documents the failure mode. Cost and auth requirements are also stated. Lacks detail on reversibility or partial-update semantics, but annotations carry the safety profile.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One dense sentence enumerates fields, then short sentences handle routing, failure, cost, and auth. Front-loaded with the core operation; every sentence earns its place with no repetition.

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 not be described. For a 14-param mutation tool with nested source object, the description covers alternative routing, auth, cost, field-level semantics, and failure behavior – everything an agent needs to call it 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?

With 64% schema coverage, description compensates by explaining the semantics of key fields (draft 'replaces; null clears', person_name 'linked only on one match', status reopen/unsnooze, snooze_until pairing). It adds meaning beyond the schema for the most ambiguous parameters, though not all 14.

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 and resource ('change one reply by reply_id') and enumerates the mutable fields (draft, summary, channel, category, received_at, person, source, status). It distinguishes itself from the sibling resolve_pending_reply by explicitly routing sent/dismissed actions there.

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?

Explicit when-to-use vs alternative: 'To mark it sent or dismissed use resolve_pending_reply.' Also gives the failure condition for unknown/other-user reply_id and the auth requirement (API key or OAuth with context.write).

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 toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources