Dayze — Life Context

Life Context Snapshot

get_life_context

Read-only

Get a snapshot of the authenticated user's current life context (identity, today/upcoming events, pulse, trackers, plus a question-aware facts slice with trace). Relationships and memories are included by default; pass include_*=false to omit. social_edges is capped at the highest-confidence 40 — check social_edges_truncated / social_edges_total. Location is opt-in. Requires an authenticated Dayze account via OAuth; scoped API keys are also supported for direct clients. ($0.15; API key required)

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Alias for query.
`at`	No	ISO date-time to answer as of (default now), e.g. 2026-09-26T09:00:00+08:00.
`query`	No	Optional question. Drives the question-aware facts slice (family, names, dates, merchants) returned in facts/trace.
`timezone`	No	IANA time zone for today (default: where the user is now, else their home zone).
`include_money`	No	Include money facts in the question-aware facts slice (opt-in; the grant must allow financial details).
`include_location`	No	Include city/country label; never returns a precise address
`include_memories`	No	Include recent memory summaries (default true; set false to omit)
`include_relationships`	No	Include inner-circle and relationship summaries (default true; set false to omit)

Output Schema

TableJSON Schema

Name	Required	Description
`facts`	No	Question-aware personal facts, in selection order.
`trace`	No	Which facts were supplied and why. fact_ids equals facts[].id.
`account`	No	The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
`omitted`	No	Facts left out, counted by reason.
`partial`	No	True when the facts slice is incomplete; never read a missing fact as "none on file".
`identity`	Yes	Account identity and timezone.
`sections`	No	sections.harness: ok, or error (HARNESS_FAILED / HARNESS_DEGRADED with failed_sources) when facts may be missing.
`redaction`	No	pii redacted\|raw; sensitive_topics the caller may receive; counts of sensitive trackers / memories withheld.
`mood_score`	No
`energy_score`	No
`inner_circle`	No
`inspect_note`	No	How to cite: link each record with its inspect_url, never a link built from an id; which record types here have no Dayze page.
`pulse_streak`	No
`social_edges`	No
`today_events`	Yes
`active_trackers`	No
`recent_memories`	No
`upcoming_events`	Yes
`pending_responses`	No
`social_edges_limit`	No	Max edges returned in social_edges.
`social_edges_total`	No	person_connections rows on file; null when unknown.
`relationship_health`	No
`social_edges_truncated`	No	True when more edges exist than social_edges lists.
`pending_responses_count`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 30, 2026

addedInput schema / properties / at

Added value: +{
+  "description": "ISO date-time to answer as of (default now), e.g. 2026-09-26T09:00:00+08:00.",
+  "type": "string"
+}

addedInput schema / properties / include_money

Added value: +{
+  "default": false,
+  "description": "Include money facts in the question-aware facts slice (opt-in; the grant must allow financial details).",
+  "type": "boolean"
+}

addedInput schema / properties / q

Added value: +{
+  "description": "Alias for query.",
+  "type": "string"
+}

addedInput schema / properties / timezone

Added value: +{
+  "description": "IANA time zone for today (default: where the user is now, else their home zone).",
+  "type": "string"
+}

Changed2 schema fields changedSep 29, 2026

addedOutput schema / properties / facts / items / properties / inspect_url

Added value: +{
+  "description": "PHI-434: the Dayze page for this record, when it has one. Cite with it.",
+  "type": "string"
+}

addedOutput schema / properties / inspect_note

Added value: +{
+  "description": "How to cite: link each record with its inspect_url, never a link built from an id; which record types here have no Dayze page.",
+  "type": "string"
+}

Changed1 schema field changedSep 26, 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"
+}

Changed3 schema fields changedSep 26, 2026

addedOutput schema / properties / social_edges_limit

Added value: +{
+  "description": "Max edges returned in social_edges.",
+  "type": "number"
+}

addedOutput schema / properties / social_edges_total

Added value: +{
+  "description": "person_connections rows on file; null when unknown.",
+  "type": [
+    "number",
+    "null"
+  ]
+}

addedOutput schema / properties / social_edges_truncated

Added value: +{
+  "description": "True when more edges exist than social_edges lists.",
+  "type": "boolean"
+}

Changed1 schema field changedSep 26, 2026

addedOutput schema / properties / redaction

Added value: +{
+  "additionalProperties": true,
+  "description": "pii redacted|raw; sensitive_topics the caller may receive; counts of sensitive trackers / memories withheld.",
+  "type": "object"
+}

Changed2 schema fields changedSep 26, 2026

addedOutput schema / properties / partial

Added value: +{
+  "description": "True when the facts slice is incomplete; never read a missing fact as \"none on file\".",
+  "type": "boolean"
+}

addedOutput schema / properties / sections

Added value: +{
+  "additionalProperties": true,
+  "description": "sections.harness: ok, or error (HARNESS_FAILED / HARNESS_DEGRADED with failed_sources) when facts may be missing.",
+  "type": "object"
+}

Changed4 schema fields changedSep 25, 2026

addedInput schema / properties / query

Added value: +{
+  "description": "Optional question. Drives the question-aware facts slice (family, names, dates, merchants) returned in facts/trace.",
+  "maxLength": 500,
+  "type": "string"
+}

addedOutput schema / properties / facts

Added value: +{
+  "description": "Question-aware personal facts, in selection order.",
+  "items": {
+    "additionalProperties": true,
+    "description": "One personal fact chosen for the question. Same ids as Dayze chat.",
+    "properties": {
+      "age_label": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "confidence": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "evidence_ref": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "id": {
+        "description": "Table-qualified record id, e.g. people:<uuid> or events:<id>.",
+        "type": "string"
+      },
+      "kind": {
+        "type": "string"
+      },
+      "last_confirmed_at": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "observed_at": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "provenance": {
+        "description": "stated, observed, inferred or imported.",
+        "type": "string"
+      },
+      "source": {
+        "type": "string"
+      },
+      "source_label": {
+        "description": "Where the fact came from, e.g. \"from Contacts\".",
+        "type": "string"
+      },
+      "source_ref": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "state": {
+        "description": "current, planned, completed, stale (age_label set) or disputed.",
+        "type": "string"
+      },
+      "text": {
+        "type": "string"
+      },
+      "tier": {
+        "description": "entity, join, static, dynamic or vector.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "kind",
+      "text",
+      "state",
+      "source_label"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / omitted

Added value: +{
+  "description": "Facts left out, counted by reason.",
+  "items": {
+    "additionalProperties": true,
+    "properties": {
+      "count": {
+        "type": "number"
+      },
+      "kind": {
+        "type": "string"
+      },
+      "reason": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "reason",
+      "kind",
+      "count"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / trace

Added value: +{
+  "additionalProperties": true,
+  "description": "Which facts were supplied and why. fact_ids equals facts[].id.",
+  "properties": {
+    "assembler": {
+      "type": "string"
+    },
+    "budget_tokens": {
+      "type": "number"
+    },
+    "caller": {
+      "type": "string"
+    },
+    "fact_ids": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "question": {
+      "type": "string"
+    },
+    "scope_key": {
+      "type": "string"
+    },
+    "selection_notes": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "used_tokens": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "fact_ids",
+    "assembler"
+  ],
+  "type": "object"
+}

Changed1 schema field changedAug 31, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "active_trackers": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "energy_score": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "identity": {
+      "additionalProperties": true,
+      "description": "Account identity and timezone.",
+      "type": "object"
+    },
+    "inner_circle": {
+      "items": {
+        "additionalProperties": true,
+        "description": "A Dayze person or contact record.",
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "mood_score": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "pending_responses": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "pending_responses_count": {
+      "type": "number"
+    },
+    "pulse_streak": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "recent_memories": {
+      "items": {
+        "additionalProperties": true,
+        "description": "A Dayze agent memory record.",
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "relationship_health": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "social_edges": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "today_events": {
+      "items": {
+        "additionalProperties": true,
+        "description": "A Dayze calendar event record.",
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "upcoming_events": {
+      "items": {
+        "additionalProperties": true,
+        "description": "A Dayze calendar event record.",
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "identity",
+    "today_events",
+    "upcoming_events"
+  ],
+  "type": "object"
+}

Changed4 schema fields changedAug 31, 2026

changedInput schema / properties / include_memories / default
```
Previous value: -falseNew value: +true
```

changedInput schema / properties / include_memories / description

Previous value: -"Include recent memory summaries"New value: +"Include recent memory summaries (default true; set false to omit)"

changedInput schema / properties / include_relationships / default
```
Previous value: -falseNew value: +true
```

changedInput schema / properties / include_relationships / description

Previous value: -"Include inner-circle and relationship summaries"New value: +"Include inner-circle and relationship summaries (default true; set false to omit)"

Changed3 schema fields changedAug 31, 2026

addedInput schema / properties / include_location

Added value: +{
+  "default": false,
+  "description": "Include city/country label; never returns a precise address",
+  "type": "boolean"
+}

addedInput schema / properties / include_memories

Added value: +{
+  "default": false,
+  "description": "Include recent memory summaries",
+  "type": "boolean"
+}

addedInput schema / properties / include_relationships

Added value: +{
+  "default": false,
+  "description": "Include inner-circle and relationship summaries",
+  "type": "boolean"
+}

First observedJul 11, 2026

TDQS

A3.9/5.0

Behavior5/5

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

Goes well beyond the readOnlyHint/destructiveHint annotations: it discloses a hard cap on social_edges with truncation signals to check (social_edges_truncated / social_edges_total), states that location is opt-in, and names the auth requirements (OAuth-authenticated account, scoped API key support) plus a price point ($0.15). These are exactly the operational facts an agent cannot recover from annotations or schema.

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 core purpose before the parenthetical detail, and each sentence carries information (contents, defaults, cap, auth, cost). It is dense with parentheticals and a trailing pricing/auth clause that slightly blurs the front-loading, but nothing is truly redundant for an 8-parameter bundle tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description correctly avoids explaining return values and instead covers what an agent still needs: scope, defaults, truncation handling, auth, and cost. The only gap is the absence of any comparison to neighboring snapshot tools, which matters given how many siblings exist.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents every parameter, including defaults and the money/location permission notes. The description's statements about defaults and 'include_*=false' largely restate the schema's own default values, adding only a small amount of framing. Baseline 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Get') and resource ('a snapshot of the authenticated user's current life context') and enumerates the bundle contents (identity, events, pulse, trackers, question-aware facts slice). An agent can tell it is a broad current-state bundle rather than a single-entity lookup. It does not explicitly name the overlapping siblings (get_context_pack, notable_pack, get_current_states), so sibling differentiation is left implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Gives concrete opt-in/opt-out guidance ('Relationships and memories are included by default; pass include_*=false to omit' and 'Location is opt-in'), which is real usage direction. However, it never says when to prefer this tool over get_context_pack, get_life_graph, or notable_pack, so the routing decision across the many snapshot-family siblings is left to inference.

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.