Skip to main content
Glama

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)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "reply_id": "<reply_id>"
    },
    "name": "update_pending_reply"
  }
}

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.
statusNoReply state, e.g. unsent.
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.
categoryNoReply category: personal or work, e.g. work.
reply_idYesFrom create_pending_reply or get_pending_replies.
person_idNoContact id, e.g. 3f2a1b4c-8d9e-6f01-c2b3-c4d5e6f70809.
request_idNoClient idempotency key (retries return original result).
person_nameNoContact name when there is no person_id, e.g. Alex Chen.
received_atNoWhen the message arrived, as ISO date-time, e.g. 2026-10-17T15:30:00Z.
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. Changed8 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"Reply category: personal or work, e.g. work."
    • addedInput schema / properties / person_id / description
      Added value: +"Contact id, e.g. 3f2a1b4c-8d9e-6f01-c2b3-c4d5e6f70809."
    • addedInput schema / properties / person_name / description
      Added value: +"Contact name when there is no person_id, e.g. Alex Chen."
    • addedInput schema / properties / received_at / description
      Added value: +"When the message arrived, as ISO date-time, e.g. 2026-10-17T15:30:00Z."
    • addedInput schema / properties / source / properties / kind / description
      Added value: +"Email source kind: gmail, email or other, e.g. gmail."
    • addedInput schema / properties / source / properties / message_id / description
      Added value: +"Email message id, e.g. 18c2a1b."
    • addedInput schema / properties / source / properties / thread_id / description
      Added value: +"Email thread id, e.g. 18c2a1b."
    • addedInput schema / properties / status / description
      Added value: +"Reply state, e.g. unsent."
  2. Changed1 schema field changed
    • changedOutput schema / properties / reply / properties / source / properties / kind / description
      Previous value: -"gmail, email or other; or imessage, whatsapp, instagram, signal, telegram when Dayze Desktop detected it (thread_id is then an opaque id)"New value: +"gmail, email or other; imessage, whatsapp, instagram, signal, telegram when Dayze Desktop detected it; or linkedin from a LinkedIn data-export import (thread_id is then an opaque id)"
  3. Changed1 schema field changed
    • changedOutput schema / properties / reply / properties / source / properties / kind / description
      Previous value: -"gmail, email or other"New value: +"gmail, email or other; or imessage, whatsapp, instagram, signal, telegram when Dayze Desktop detected it (thread_id is then an opaque id)"
  4. 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."
  5. 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"
      +}
  6. 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"
      +]
  7. 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"
      +  ]
      +}
  8. Changed1 schema field changed
    • addedInput schema / properties / draft_message
      Added value: +{
      +  "description": "Alias for draft.",
      +  "type": "string"
      +}
  9. 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"
      +]
  10. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the not_found error for unknown or other-user reply_ids, the auth requirement (API key or OAuth with context.write), the $0.10 cost, and the guarantee that nothing is sent. The 'null clears' semantics on draft and source are also surfaced, which matters given destructiveHint=false.

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-loads the identity and the field list in one dense sentence, then follows with error, alternative, safety, and auth in priority order. The semicolon-heavy enumeration and trailing '($0.10; API key required)' read as compressed rather than wasteful.

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 14-parameter mutation with a nested source object and an output schema, the description covers everything an agent needs: identity, mutable surface, null-clearing behavior, failure mode, auth, cost, and the sibling to use for send/dismiss. Return values are legitimately left to the output schema.

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 already 100%, so the baseline is 3, but the description adds real meaning: it groups the updatable fields, notes draft replaces and null clears, and explains that person_name is linked only on a single match. Derived alias behavior (draft_message, idempotency_key) is left to the schema.

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, so an agent knows exactly what is being updated. It also names the sibling it is not ('To mark it sent or dismissed use resolve_pending_reply'), separating it cleanly from resolve_pending_reply and create_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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the sent/dismissed case to resolve_pending_reply, which is the highest-risk confusion among siblings, and clarifies the tool never sends anything. It does not explicitly cover when to use create_pending_reply vs this tool, but the 'change one reply by reply_id' framing implies it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.