Dayze — Life Context

Life Update Interactions

get_interactions

Read-only

Bounded graph read over life_updates (PHI-54/61): traverse interaction → person/event/expense/place with source/confidence on every hop. When life_update edges are missing, projects hops from CRM interactions, event_people, and expense person FKs (PHI-100). Prefer for “who was I with at X?”, “when am I meeting Y next?”, “how much at Z?”. 93-day default window. Pass person_name, place_query, or ids. 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.10; API key required)

Input Schema

TableJSON Schema

Name	Required	Description
`to`	No	Inclusive YYYY-MM-DD
`from`	No	Inclusive YYYY-MM-DD
`limit`	No	Max 1–50, default 25
`event_id`	No
`place_id`	No
`person_id`	No
`expense_id`	No
`person_name`	No
`place_query`	No	Venue/merchant substring

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	No
`error`	No
`window`	No	Bounded from/to lookback window.
`account`	No	The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
`no_data`	No
`degraded`	No
`truncated`	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.
`interactions`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 3, 2026
- addedOutput schema / properties / degraded
```
Added value: +{
+  "type": "boolean"
+}
```

Changed2 schema fields changedSep 29, 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 / 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"
+}

AddedSep 19, 2026

TDQS

A4.3/5.0

Behavior5/5

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

With annotations already covering readOnly/non-destructive/closed-world, the description adds substantial extra context: a 93-day default window, fallback projection from CRM interactions/event_people/expense FKs, per-record inspect_url citation rules, cost ($0.10), and API-key requirement.

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: the core purpose leads, then fallback behavior, then usage triggers, then operational constraints. Nearly every sentence carries information, though the parenthetical ticket references (PHI-54/61, PHI-100) are noise for an agent.

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, return-value detail is unnecessary, and the description covers fallback behavior, citation rules, cost, and auth. Minor gap: it doesn't clarify how explicit from/to overrides the 93-day default or how the several id filters combine.

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 only 44% across 9 parameters, so the schema leaves gaps. The description adds the useful hint to pass person_name, place_query, or ids and mentions the 93-day default window, but does not explain the id parameters, limit semantics, or how from/to interact with the default window.

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 ('Bounded graph read over life_updates') and names the exact traversal path (interaction → person/event/expense/place). This clearly distinguishes it from siblings like get_life_graph and get_person_interactions.

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 explicit trigger questions ('who was I with at X?', 'when am I meeting Y next?', 'how much at Z?') and an edge-case fallback behavior for missing life_update edges. It does not name a sibling alternative or state when NOT to use it, so it falls short of a 5.

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.