Dayze MCP

Life Context Snapshot

get_life_context

Read-only

Get a user's life context: identity, events, pulse, trackers, relationships, memories. Give AI agents a complete view of the user's day for personalized responses.

Instructions

Get a snapshot of the authenticated user's current life context (identity, today/upcoming events, pulse, trackers). Relationships and memories are included by default; pass include_*=false to omit. 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
`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
`identity`	Yes	Account identity and timezone.
`mood_score`	No
`energy_score`	No
`inner_circle`	No
`pulse_streak`	No
`social_edges`	No
`today_events`	Yes
`active_trackers`	No
`recent_memories`	No
`upcoming_events`	Yes
`pending_responses`	No
`relationship_health`	No
`pending_responses_count`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.28.0Sep 16, 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": true,
+  "description": "Include recent memory summaries (default true; set false to omit)",
+  "type": "boolean"
+}

addedInput schema / properties / include_relationships

Added value: +{
+  "default": true,
+  "description": "Include inner-circle and relationship summaries (default true; set false to omit)",
+  "type": "boolean"
+}

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

First observedv1.6.2Jul 18, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already mark the tool as read-only and non-destructive, and the description adds meaningful context: authentication requirements via OAuth or scoped API keys, cost, and default inclusion behavior. This goes beyond the structured annotations and aligns with them, with no contradiction.

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?

The description is three concise sentences that front-load the purpose and then cover defaults and auth/cost. Every sentence adds useful information without redundancy or filler.

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?

For a read-only tool with zero required parameters, an output schema, and safe annotations, the description adequately covers defaults, opt-in location, and authentication. It is slightly thin on routing to more granular sibling tools, but an agent has enough to invoke the tool correctly.

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 all three boolean parameters are already documented with defaults. The description reinforces the include_*=false pattern and the opt-in nature of location, but adds little new meaning beyond the structured schema. This fits the baseline where 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?

The description uses a specific verb ('Get') and names a composite resource ('snapshot of the authenticated user's current life context') with enumerated contents: identity, today/upcoming events, pulse, trackers. It also clarifies the optional relationship, memory, and location buckets. It does not explicitly differentiate from sibling tools like get_context_pack, so it is clear but not maximally distinct.

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?

The description explains that relationships and memories are included by default and can be omitted via include_*=false, and that location is opt-in. This gives practical call-construction guidance but no explicit when-to-use versus alternatives such as get_memories, get_events, or get_trackers. Usage is implied by 'snapshot' rather than stated with exclusions.

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

Deploy Server