Dayze — Life Context

Life Context Pack

get_context_pack

Read-only

Life Context pack for one Dayze account (account names it — with more than one Dayze connection, say which account you are answering from): identity, pulse, people, next actions, memories, quizzes, recent consented place visits, and traced facts. Use include_*=false to omit default sections; current location and money stay opt-in. Spec: https://dayze.com/docs/life-context Records carry inspect_url (their Dayze page): cite with it, never build a link from an id; a record without one has no page (inspect_note says which). ($0.20; API key required)

Input 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.
`focus`	No	Optional focus hint echoed in the pack (e.g. places, travel, people)
`query`	No	Question that guides facts and memories.
`timezone`	No	IANA time zone for today (default: where the user is now, else their home zone).
`budget_tokens`	No	Whole-pack token budget (clamped to 300–12000); list omissions are recorded in budget.sections.
`include_money`	No	Include the private cashflow summary
`include_trips`	No	Include up to 10 stored trips via get_trips (no inferred trips); count is returned items, total/has_more/next_cursor expose paging, budget.sections exposes token cuts
`include_places`	No	Include recent canonical places.
`include_location`	No	Include city/country label; never returns a precise address
`include_memories`	No	Include recent memories.
`include_week_events`	No	Include calendar-week events; defaults on except focus next_actions/current/now. False keeps an empty compatibility list with omitted_for_focus semantics.
`include_place_visits`	No	Include recent venue visits; never a GPS trail
`include_quiz_results`	No	Include latest quiz results.
`include_relationships`	No	Include people and relationship context.

Output Schema

Name	Required	Description
`ok`	No
`error`	No	Present when life state is unavailable.
`facts`	No	Question-aware personal facts, in selection order.
`focus`	No
`pulse`	Yes
`query`	No
`trace`	No	Which facts were supplied and why. fact_ids equals facts[].id.
`trips`	No	Stored trips when include_trips=true; items/count, limit, total/has_more/next_cursor. Budget cuts are in budget.sections.
`budget`	No	Whole-pack token budget and per-list truncation ledger: budget_tokens is the effective budget, requested_tokens what was sent (null if none), adjustment why they differ (clamped_to_min, clamped_to_max, rounded_down, invalid_used_default).
`places`	No	Recent canonical places when include_places=true.
`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
`identity`	Yes
`location`	No	City/country-only get_location_context projection when include_location=true.
`memories`	No
`protocol`	Yes	Life Context metadata.
`sections`	No	Per-section ok/error status for partial packs.
`redaction`	No	pii redacted\|raw; sensitive_topics the caller may receive; counts of sensitive trackers / memories withheld.
`whats_next`	Yes	Calendar buckets, trackers, goals and replies. With include_money: money (summary or null) and money_status: ok, no_data, not_shared (privacy settings withhold money aggregates) or unavailable.
`known_facts`	No
`who_matters`	No
`generated_at`	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.
`place_visits`	No
`quiz_results`	No	Latest results when include_quiz_results=true; items/count and limit.
`preferred_tool`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 27, 2026

changedOutput schema / properties / budget / description

Previous value: -"Whole-pack token budget and per-list truncation ledger."New value: +"Whole-pack token budget and per-list truncation ledger: budget_tokens is the effective budget, requested_tokens what was sent (null if none), adjustment why they differ (clamped_to_min, clamped_to_max, rounded_down, invalid_used_default)."

addedOutput schema / properties / whats_next / description

Added value: +"Calendar buckets, trackers, goals and replies. With include_money: money (summary or null) and money_status: ok, no_data, not_shared (privacy settings withhold money aggregates) or unavailable."

Changed7 schema fields changedOct 27, 2026

addedInput schema / properties / budget_tokens

Added value: +{
+  "description": "Whole-pack token budget (clamped to 300–12000); list omissions are recorded in budget.sections.",
+  "type": "number"
+}

changedInput schema / properties / include_trips / description

Previous value: -"Include recent/upcoming trips from completed travel history"New value: +"Include up to 10 stored trips via get_trips (no inferred trips); count is returned items, total/has_more/next_cursor expose paging, budget.sections exposes token cuts"

addedInput schema / properties / include_week_events

Added value: +{
+  "description": "Include calendar-week events; defaults on except focus next_actions/current/now. False keeps an empty compatibility list with omitted_for_focus semantics.",
+  "type": "boolean"
+}

addedOutput schema / properties / budget

Added value: +{
+  "additionalProperties": true,
+  "description": "Whole-pack token budget and per-list truncation ledger.",
+  "type": "object"
+}

addedOutput schema / properties / location

Added value: +{
+  "additionalProperties": true,
+  "description": "City/country-only get_location_context projection when include_location=true.",
+  "type": "object"
+}

addedOutput schema / properties / quiz_results

Added value: +{
+  "additionalProperties": true,
+  "description": "Latest results when include_quiz_results=true; items/count and limit.",
+  "type": "object"
+}

changedOutput schema / properties / trips / description

Previous value: -"Recent trips when include_trips=true."New value: +"Stored trips when include_trips=true; items/count, limit, total/has_more/next_cursor. Budget cuts are in budget.sections."

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

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

Changed1 schema field changedSep 26, 2026
- changedOutput schema / properties / protocol / description
```
Previous value: -"Life Context Protocol metadata."New value: +"Life Context metadata."
```

Changed7 schema fields changedSep 26, 2026

changedInput schema / properties / include_memories / description

Previous value: -"Include recent memories (default true; false wins even with a query)."New value: +"Include recent memories."

addedInput schema / properties / include_place_visits

Added value: +{
+  "default": true,
+  "description": "Include recent venue visits; never a GPS trail",
+  "type": "boolean"
+}

changedInput schema / properties / include_places / description

Previous value: -"Include recent canonical places (venue-level, no GPS points)"New value: +"Include recent canonical places."

changedInput schema / properties / include_quiz_results / description

Previous value: -"Include latest quiz results (slug, result_type, result_data)."New value: +"Include latest quiz results."

changedInput schema / properties / include_relationships / description

Previous value: -"Include who_matters (inner-circle, relationship health, reach-out)."New value: +"Include people and relationship context."

changedInput schema / properties / query / description

Previous value: -"Optional question; drives facts/trace (family, names, dates, merchants) and memories."New value: +"Question that guides facts and memories."

addedOutput schema / properties / place_visits

Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "description": "Recent place visit.",
+    "type": "object"
+  },
+  "type": "array"
+}

Changed1 schema field changedSep 26, 2026

changedOutput schema / properties / known_facts / items / description

Previous value: -"A personal fact Dayze currently serves: ref, kind, text, source. Read live; disputed or no-longer-true facts are left out."New value: +"A correctable contact, learned fact or memory from the facts slice: ref (in trace.fact_ids), kind, text, source. Disputed or no-longer-true facts are left out."

Changed7 schema fields changedSep 25, 2026

changedInput schema / properties / include_memories / description

Previous value: -"Include recent memories (default true). A query always enables focused memories."New value: +"Include recent memories (default true; false wins even with a query)."

changedInput schema / properties / include_quiz_results / description

Previous value: -"Include latest quiz results (slug, result_type, result_data). Default true."New value: +"Include latest quiz results (slug, result_type, result_data)."

changedInput schema / properties / include_relationships / description

Previous value: -"Include who_matters (inner-circle, relationship health, reach-out). Default true."New value: +"Include who_matters (inner-circle, relationship health, reach-out)."

changedInput schema / properties / query / description

Previous value: -"Optional focus query for semantic memories"New value: +"Optional question; drives facts/trace (family, names, dates, merchants) and memories."

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 changedSep 25, 2026

addedOutput schema / properties / known_facts

Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "description": "A personal fact Dayze currently serves: ref, kind, text, source. Read live; disputed or no-longer-true facts are left out.",
+    "type": "object"
+  },
+  "type": "array"
+}

Changed1 schema field changedSep 14, 2026

addedInput schema / properties / include_quiz_results

Added value: +{
+  "default": true,
+  "description": "Include latest quiz results (slug, result_type, result_data). Default true.",
+  "type": "boolean"
+}

Changed5 schema fields changedSep 3, 2026

addedOutput schema / properties / error

Added value: +{
+  "description": "Present when life state is unavailable.",
+  "type": "string"
+}

addedOutput schema / properties / generated_at
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / ok
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / partial
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / sections

Added value: +{
+  "additionalProperties": true,
+  "description": "Per-section ok/error status for partial packs.",
+  "type": "object"
+}

Changed6 schema fields changedSep 1, 2026

addedInput schema / properties / focus

Added value: +{
+  "description": "Optional focus hint echoed in the pack (e.g. places, travel, people)",
+  "type": "string"
+}

addedInput schema / properties / include_places

Added value: +{
+  "default": false,
+  "description": "Include recent canonical places (venue-level, no GPS points)",
+  "type": "boolean"
+}

addedInput schema / properties / include_trips

Added value: +{
+  "default": false,
+  "description": "Include recent/upcoming trips from completed travel history",
+  "type": "boolean"
+}

addedOutput schema / properties / focus

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / places

Added value: +{
+  "additionalProperties": true,
+  "description": "Recent canonical places when include_places=true.",
+  "type": "object"
+}

addedOutput schema / properties / trips

Added value: +{
+  "additionalProperties": true,
+  "description": "Recent trips when include_trips=true.",
+  "type": "object"
+}

Changed1 schema field changedAug 31, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "identity": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "memories": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "preferred_tool": {
+      "type": "string"
+    },
+    "protocol": {
+      "additionalProperties": true,
+      "description": "Life Context Protocol metadata.",
+      "type": "object"
+    },
+    "pulse": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "query": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "whats_next": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "who_matters": {
+      "additionalProperties": true,
+      "type": "object"
+    }
+  },
+  "required": [
+    "protocol",
+    "preferred_tool",
+    "identity",
+    "pulse",
+    "whats_next"
+  ],
+  "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 memories when no query is provided; a query always enables focused memories"New value: +"Include recent memories (default true). A query always enables focused memories."

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

changedInput schema / properties / include_relationships / description

Previous value: -"Include inner-circle, relationship health, and reach-out suggestions"New value: +"Include who_matters (inner-circle, relationship health, reach-out). Default true."

Changed4 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 memories when no query is provided; a query always enables focused memories",
+  "type": "boolean"
+}

addedInput schema / properties / include_money

Added value: +{
+  "default": false,
+  "description": "Include the private cashflow summary",
+  "type": "boolean"
+}

addedInput schema / properties / include_relationships

Added value: +{
+  "default": false,
+  "description": "Include inner-circle, relationship health, and reach-out suggestions",
+  "type": "boolean"
+}

AddedJul 14, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly/non-destructive/closed-world, so the bar is lower, yet the description still adds material context: a $0.20 cost, an API key requirement, the guarantee that no precise address is returned, and the inspect_url citation rule with the inspect_note fallback. That is genuine behavioral disclosure beyond the structured fields, though paging/truncation behavior is only implied via the 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?

Dense but front-loaded: contents first, then defaults/opt-ins, then the citation rule, then cost and auth. The parenthetical asides and the mid-sentence spec URL interrupt flow slightly, but no sentence is 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 15-parameter, zero-required, output-schema-backed aggregate tool, the description covers the parts the schema cannot: default section behavior, the citation contract for inspect_url, cost, and auth. The remaining gap is the `account` selection mechanism, which is mentioned but not resolvable from any parameter.

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 baseline is 3; the description earns above that by explaining the include_*=false opt-out model and clarifying that location and money are non-default, which frames how the 15 boolean toggles should be reasoned about collectively. It does not, however, add anything for query/at/timezone/budget_tokens beyond the schema, and it references an `account` name that has no corresponding parameter in the schema.

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 enumerates exactly what the pack contains (identity, pulse, people, next actions, memories, quizzes, place visits, traced facts), which is far more specific than the title. However, it never distinguishes itself from close siblings such as get_life_context, get_today, or notable_pack, and it opens with a noun phrase rather than a verb, so an agent must infer the action.

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?

It gives real operating guidance: use include_*=false to omit default sections, location and money are opt-in only, and when multiple Dayze connections exist the agent must state which account it is answering from. What is missing is any when-not or alternative routing against the many overlapping read tools in the sibling list.

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.

Life Context Pack

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources