Dayze — Life Context

Log Interaction

log_interaction

Contacts: log that the user was in touch with a contact ('I replied to Vadim', 'called Mum'): kind message, call, meeting, note, check_in or thought_of. Private to the owner. person_id (an owned contact) or person_name (linked only on one resolve_person match; otherwise nothing is logged and the candidates come back). With reply_id it also marks that Pending Reply sent: this interaction is the reply's one write-back (a later resolve adds no second). summary: one line in your own words, never email text or a subject. occurred_at: when it happened (ISO), default now; not in the future. Never sends anything. Requires API key or OAuth with context.write. ($0.05; API key required)

Input Schema

Name	Required	Description
`kind`	No	Default message.
`summary`	No	One line (max 280) in your own words. Never the email body, subject or sender.
`reply_id`	No	A Pending Reply (get_pending_replies) this closes as sent.
`person_id`	No	An owned contact id.
`request_id`	No	Client idempotency key (retries return original result).
`occurred_at`	No	When it happened (ISO date-time). Default now.
`person_name`	No	The contact as the user said it ("Vadim"); linked only on one match.
`idempotency_key`	No	Alias for request_id.

Output 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.
`created`	Yes	False when it was already stored (a retry, or the reply's write-back).
`message`	Yes
`provenance`	No	Which connector wrote the record and which connected Dayze account received it.
`inspect_url`	No	The Dayze page that shows the saved record.
`interaction`	Yes	The interaction in the contact's history (private to the owner).
`inspect_note`	No	What inspect_url opens. Never quote the record id.
`reply_resolved`	Yes	True when this call marked the reply sent.
`life_state_rebuilt`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 21, 2026

addedOutput schema / properties / inspect_note

Added value: +{
+  "description": "What inspect_url opens. Never quote the record id.",
+  "type": "string"
+}

addedOutput schema / properties / inspect_url

Added value: +{
+  "description": "The Dayze page that shows the saved record.",
+  "type": "string"
+}

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

AddedSep 30, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only say write, non-destructive, closed-world; the description adds far more: auth requirement (API key or OAuth with context.write), per-call cost, that it never sends anything, that a non-unique person_name match logs nothing and returns candidates, and that a later resolve adds no second write-back. That is exactly the behavioral context the annotations do not carry.

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-loaded with the core action and example intents, and virtually every clause carries operational meaning. It is a dense, parenthesis-heavy paragraph rather than a cleanly chunked one, which costs a little readability for an 8-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?

Given an output schema exists, the description needn't explain returns; it instead covers the remaining gaps: cost, auth scope, idempotency behavior, identity-resolution failure mode, and the summary/occurred_at constraints. An agent has everything needed to call this 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?

Schema coverage is 100%, so the baseline is 3, but the description goes beyond the schema by constraining semantics: occurred_at cannot be in the future, summary must never be email body/subject/sender, person_name links only on a single resolve_person match, and reply_id is the reply's single write-back. It does not explain request_id/idempotency_key, which the schema already covers.

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 ('log that the user was in touch with a contact') plus concrete triggering utterances and the enumerated kinds, which cleanly separates it from siblings such as log_event or log_entry. An agent can identify the operation 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 Guidelines4/5

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

Gives clear usage context with example phrasings and constraints (private to the owner, never email text or a subject, not in the future), plus the person_id vs person_name selection rule and the reply_id write-back case. It does not name a sibling tool to use instead for adjacent logging tasks, so routing is inferred rather than explicit.

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

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.