Dayze — Life Context

Agent Memories

get_memories

Read-only

Authenticated user memories from Dayze Agent. Pass query for semantic/keyword retrieval. Prefer search for event-first trip and calendar titles. Requires OAuth or a supported scoped credential. ($0.10; API key required)

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Alias for query.
`focus`	No	Ranks memories toward this focus. next_actions (or current, now) returns only up to 4 next-action memories.
`limit`	No	Max rows 1–50, default 20
`query`	No	Semantic focus (optional)

Output Schema

TableJSON Schema

Name	Required	Description
`mode`	Yes
`query`	No
`events`	No
`people`	No
`account`	No	The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
`memories`	Yes
`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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 30, 2026

addedInput schema / properties / focus

Added value: +{
+  "description": "Ranks memories toward this focus. next_actions (or current, now) returns only up to 4 next-action memories.",
+  "type": "string"
+}

addedInput schema / properties / q

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

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

Changed1 schema field changedAug 31, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "events": {
+      "items": {
+        "additionalProperties": true,
+        "description": "A Dayze calendar event record.",
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "memories": {
+      "items": {
+        "additionalProperties": true,
+        "description": "A Dayze agent memory record.",
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "mode": {
+      "enum": [
+        "semantic",
+        "keyword",
+        "blended",
+        "chronological"
+      ],
+      "type": "string"
+    },
+    "people": {
+      "items": {
+        "additionalProperties": true,
+        "description": "A Dayze person or contact record.",
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "query": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "mode",
+    "memories"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedJul 14, 2026

addedInput schema / properties / limit

Added value: +{
+  "description": "Max rows 1–50, default 20",
+  "type": "number"
+}

addedInput schema / properties / query

Added value: +{
+  "description": "Semantic focus (optional)",
+  "type": "string"
+}

First observedJul 11, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: an auth requirement ('OAuth or a supported scoped credential') and a cost/credential gate ('$0.10; API key required'), which an agent needs before invoking.

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?

Four short, front-loaded clauses with zero filler: purpose, usage, alternative routing, and auth/cost. Every sentence carries distinct information; nothing is repeated from the schema or annotations.

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?

An output schema exists, so return-value explanation is unnecessary. Auth, cost, and search-vs-memories routing are all present. Only minor gaps remain around what a 'memory' record contains conceptually, but that is largely covered by the schema and output schema.

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 q/query, focus, and limit. The description only mentions that query drives semantic/keyword retrieval, adding little beyond the schema's own text. Baseline 3 applies.

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 the verb (retrieve) and resource (authenticated user memories from Dayze Agent) and names the sibling 'search' as the contrasting tool. An agent can tell what this returns without opening the schema, though the nature of a 'memory' is left somewhat abstract.

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?

'Prefer search for event-first trip and calendar titles' gives an explicit alternative and the condition that selects it, and 'Pass query for semantic/keyword retrieval' implies the primary usage. No explicit when-not for get_memories itself, but the routing is clear.

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.