Dayze — Life Context

Semantic Life Search

search

Read-only

Search the authenticated user life graph. Optional from/to (aliases start/end) are inclusive account-local civil dates on every search route; either bound may be used alone. Dated semantic and keyword records use event date, expense date, goal start date, check-in date, or the account-local creation date of contacts and memories. Deterministic routing first: food or relative dates (e.g. "what did I eat yesterday?"); timeline/current-context; money+person; who-is → resolve_person. Otherwise semantic/keyword search. Event hits include event_date and food_id when mirrored from Food Diary. Browser-history titles are excluded. Credential/secret spans are redacted. 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). Requires OAuth or a supported scoped credential. ($0.15; API key required)

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Alias for query.
`to`	No	Inclusive account-local YYYY-MM-DD upper bound for all search routes. May be used alone.
`end`	No	Alias for to.
`from`	No	Inclusive account-local YYYY-MM-DD lower bound for all search routes. May be used alone.
`limit`	No	Max results 1–50
`query`	No	Primary search query.
`start`	No	Alias for from.
`entity_type`	No	Route a Moment query to search_moments.

Output Schema

TableJSON Schema

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

Changed1 schema field changedOct 3, 2026

addedInput schema / properties / entity_type

Added value: +{
+  "description": "Route a Moment query to search_moments.",
+  "enum": [
+    "moment"
+  ],
+  "type": "string"
+}

Changed2 schema fields changedOct 3, 2026

changedInput schema / properties / from / description

Previous value: -"Inclusive YYYY-MM-DD start for structured food search. Pair with to."New value: +"Inclusive account-local YYYY-MM-DD lower bound for all search routes. May be used alone."

changedInput schema / properties / to / description

Previous value: -"Inclusive YYYY-MM-DD end for structured food search. Pair with from."New value: +"Inclusive account-local YYYY-MM-DD upper bound for all search routes. May be used alone."

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

addedOutput schema / properties / results / items / properties / inspect_url

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

Changed3 schema fields changedSep 29, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "end": {
-        "description": "Alias for to.",
-        "type": "string"
-      },
-      "from": {
-        "description": "Inclusive YYYY-MM-DD start for structured food search. Pair with to.",
-        "type": "string"
-      },
-      "limit": {
-        "default": 10,
-        "description": "Max results 1–50",
-        "type": "number"
-      },
-      "q": {
-        "description": "Alias for query.",
-        "type": "string"
-      },
-      "query": {
-        "description": "Primary search query.",
-        "type": "string"
-      },
-      "start": {
-        "description": "Alias for from.",
-        "type": "string"
-      },
-      "to": {
-        "description": "Inclusive YYYY-MM-DD end for structured food search. Pair with from.",
-        "type": "string"
-      }
-    },
-    "required": [
-      "query"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "end": {
-        "description": "Alias for to.",
-        "type": "string"
-      },
-      "from": {
-        "description": "Inclusive YYYY-MM-DD start for structured food search. Pair with to.",
-        "type": "string"
-      },
-      "limit": {
-        "default": 10,
-        "description": "Max results 1–50",
-        "type": "number"
-      },
-      "q": {
-        "description": "Alias for query.",
-        "type": "string"
-      },
-      "query": {
-        "description": "Primary search query.",
-        "type": "string"
-      },
-      "start": {
-        "description": "Alias for from.",
-        "type": "string"
-      },
-      "to": {
-        "description": "Inclusive YYYY-MM-DD end for structured food search. Pair with from.",
-        "type": "string"
-      }
-    },
-    "required": [
-      "q"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "required": [
+      "query"
+    ]
+  },
+  {
+    "required": [
+      "q"
+    ]
+  }
+]

addedInput schema / properties

Added value: +{
+  "end": {
+    "description": "Alias for to.",
+    "type": "string"
+  },
+  "from": {
+    "description": "Inclusive YYYY-MM-DD start for structured food search. Pair with to.",
+    "type": "string"
+  },
+  "limit": {
+    "default": 10,
+    "description": "Max results 1–50",
+    "type": "number"
+  },
+  "q": {
+    "description": "Alias for query.",
+    "type": "string"
+  },
+  "query": {
+    "description": "Primary search query.",
+    "type": "string"
+  },
+  "start": {
+    "description": "Alias for from.",
+    "type": "string"
+  },
+  "to": {
+    "description": "Inclusive YYYY-MM-DD end for structured food search. Pair with from.",
+    "type": "string"
+  }
+}

Changed1 schema field changedSep 26, 2026

changedInput schema / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "limit": {
-        "default": 10,
-        "description": "Max results 1–50",
-        "type": "number"
-      },
-      "q": {
-        "description": "Alias for query.",
-        "type": "string"
-      },
-      "query": {
-        "description": "Primary search query.",
-        "type": "string"
-      }
-    },
-    "required": [
-      "query"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "limit": {
-        "default": 10,
-        "description": "Max results 1–50",
-        "type": "number"
-      },
-      "q": {
-        "description": "Alias for query.",
-        "type": "string"
-      },
-      "query": {
-        "description": "Primary search query.",
-        "type": "string"
-      }
-    },
-    "required": [
-      "q"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "end": {
+        "description": "Alias for to.",
+        "type": "string"
+      },
+      "from": {
+        "description": "Inclusive YYYY-MM-DD start for structured food search. Pair with to.",
+        "type": "string"
+      },
+      "limit": {
+        "default": 10,
+        "description": "Max results 1–50",
+        "type": "number"
+      },
+      "q": {
+        "description": "Alias for query.",
+        "type": "string"
+      },
+      "query": {
+        "description": "Primary search query.",
+        "type": "string"
+      },
+      "start": {
+        "description": "Alias for from.",
+        "type": "string"
+      },
+      "to": {
+        "description": "Inclusive YYYY-MM-DD end for structured food search. Pair with from.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "query"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "end": {
+        "description": "Alias for to.",
+        "type": "string"
+      },
+      "from": {
+        "description": "Inclusive YYYY-MM-DD start for structured food search. Pair with to.",
+        "type": "string"
+      },
+      "limit": {
+        "default": 10,
+        "description": "Max results 1–50",
+        "type": "number"
+      },
+      "q": {
+        "description": "Alias for query.",
+        "type": "string"
+      },
+      "query": {
+        "description": "Primary search query.",
+        "type": "string"
+      },
+      "start": {
+        "description": "Alias for from.",
+        "type": "string"
+      },
+      "to": {
+        "description": "Inclusive YYYY-MM-DD end for structured food search. Pair with from.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "q"
+    ],
+    "type": "object"
+  }
+]

Changed1 schema field changedSep 26, 2026

addedOutput schema / properties / results / items / properties / photo_url

Added value: +{
+  "description": "Meal photo on a food result, when one is attached.",
+  "type": "string"
+}

Changed4 schema fields changedSep 3, 2026
- changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +false
```
- changedOutput schema / properties / results / items / additionalProperties
```
Previous value: -trueNew value: +false
```
- changedOutput schema / properties / results / items / properties / event_date / type
```
Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
```
- changedOutput schema / properties / results / items / properties / food_id / type
```
Previous value: -[
-  "string",
-  "null"
-]New value: +"string"
```

Changed4 schema fields changedSep 1, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / anyOf

Added value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "limit": {
+        "default": 10,
+        "description": "Max results 1–50",
+        "type": "number"
+      },
+      "q": {
+        "description": "Alias for query.",
+        "type": "string"
+      },
+      "query": {
+        "description": "Primary search query.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "query"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "limit": {
+        "default": 10,
+        "description": "Max results 1–50",
+        "type": "number"
+      },
+      "q": {
+        "description": "Alias for query.",
+        "type": "string"
+      },
+      "query": {
+        "description": "Primary search query.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "q"
+    ],
+    "type": "object"
+  }
+]

removedInput schema / properties

Removed value: -{
-  "limit": {
-    "default": 10,
-    "description": "Max results 1–50",
-    "type": "number"
-  },
-  "q": {
-    "description": "Alias for query",
-    "type": "string"
-  },
-  "query": {
-    "description": "Search query (primary)",
-    "type": "string"
-  }
-}

removedInput schema / required
```
Removed value: -[
-  "query"
-]
```

Changed4 schema fields changedAug 31, 2026

changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +true
```
addedOutput schema / properties / intent
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / mode / enum

Previous value: -[
-  "semantic",
-  "keyword",
-  "blended"
-]New value: +[
+  "semantic",
+  "keyword",
+  "blended",
+  "structured"
+]

changedOutput schema / properties / results / items / additionalProperties
```
Previous value: -falseNew value: +true
```

Changed1 schema field changedAug 31, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "mode": {
+      "enum": [
+        "semantic",
+        "keyword",
+        "blended"
+      ],
+      "type": "string"
+    },
+    "results": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "content": {
+            "type": "string"
+          },
+          "event_date": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "food_id": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "similarity": {
+            "type": "number"
+          },
+          "source_id": {
+            "type": "string"
+          },
+          "source_type": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "source_type",
+          "source_id",
+          "title",
+          "content",
+          "similarity"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "mode",
+    "results"
+  ],
+  "type": "object"
+}

First observedJul 11, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations declare readOnlyHint=true and destructiveHint=false, so the safety profile is already covered. The description adds substantive behavior beyond that: date semantics per record type, event_date/food_id inclusion, browser-history exclusion, credential-span redaction, inspect_url semantics (never build links from ids; inspect_note marks records without a page), auth requirements, and cost. That is a lot of high-value behavioral context not available elsewhere.

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 and front-loaded, starting with what it searches and then moving through date semantics, routing, behavior, and auth. Every sentence carries information, but the routing and date-semantics passages are compressed to the point of being hard to parse on a single read.

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

Completeness5/5

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

Given the complexity (8 params, aliases, routing, citations, auth, cost) and the presence of an output schema, the description covers everything an agent needs to call the tool correctly and interpret its results. Nothing material is missing.

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 the baseline is 3, but the description adds real value on top of the schema: from/to aliases (start/end) and their inclusive, account-local civil-date semantics, single-bound usage, and the mapping between date bounds and specific record date fields. It does not separately cover all 8 parameters (e.g. limit, entity_type routing is mentioned only implicitly), so it is strong but not exhaustive.

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?

The description states a specific action (search) and resource (authenticated user life graph) and then describes a deterministic routing layer that maps query shapes to tools (food/relative dates → timeline; money+person; who-is → resolve_person; otherwise semantic/keyword). This clearly distinguishes the tool from the large set of sibling search_* and get_* tools.

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

Usage Guidelines5/5

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

Explicitly states when to use this tool (fallback after deterministic routing) versus when routing sends the query elsewhere. The routing rules are self-contained and executable without reading sibling tools. This is about as strong as usage guidance can be.

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.