Dayze — Life Context

Search Transactions

search_transactions

Read-only

Search individual transaction rows by merchant/description/category, or exact tag (project:/ext:/rail:). Requires context.read and financial_details:read. ($0.10; API key required)

Input Schema

TableJSON Schema

Name	Required	Description
`tag`	No
`limit`	No	Page size 1-500, default 100.
`query`	No
`cursor`	No	Continue the same immutable one-hour snapshot; other filters remain frozen.
`offset`	No	Skip this many rows of a new snapshot (a cursor carries its own).
`project`	No
`include_archived`	No

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 30, 2026

changedInput schema / additionalProperties
```
Previous value: -trueNew value: +false
```
addedInput schema / properties / limit / description
```
Added value: +"Page size 1-500, default 100."
```

addedInput schema / properties / offset

Added value: +{
+  "description": "Skip this many rows of a new snapshot (a cursor carries its own).",
+  "type": "number"
+}

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

Changed2 schema fields changedSep 16, 2026

addedInput schema / properties / cursor

Added value: +{
+  "description": "Continue the same immutable one-hour snapshot; other filters remain frozen.",
+  "type": "string"
+}

addedInput schema / properties / include_archived
```
Added value: +{
+  "type": "boolean"
+}
```

Changed3 schema fields changedSep 13, 2026
- addedInput schema / properties / limit
```
Added value: +{
+  "type": "number"
+}
```
- addedInput schema / properties / project
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / tag
```
Added value: +{
+  "type": "string"
+}
```
AddedSep 1, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Goes beyond the read-only/destructive annotations by disclosing required scopes (context.read, financial_details:read), a per-call cost ($0.10), and API-key auth. These are genuinely useful operational facts an agent can't get from structured fields. It stops short of describing snapshot/pagination behavior, which is left to 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?

One dense sentence front-loads the core search capability, then appends auth/cost requirements. No wasted words, though the parenthetical auth/cost tail is compact enough to be easily missed.

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 values need no explanation, and the description covers purpose, scopes, cost, and key filter semantics. The main gap is the absence of sibling routing guidance (get_transactions vs this search).

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?

Adds real meaning to the undocumented 'tag' param by naming the exact prefix syntax (project:/ext:/rail:) and clarifies that query covers merchant/description/category. However, with only 43% schema coverage, limit, cursor, offset, project, and include_archived remain unaddressed in the description.

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 a specific verb (Search) and resource (individual transaction rows) and enumerates the searchable fields (merchant/description/category, exact tag). 'Individual transaction rows' implicitly distinguishes it from aggregate siblings like get_transactions, though it never names an alternative.

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?

Usage is only implied: the presence of a query/tag filter signals 'use this when you have search criteria.' It never states when to prefer this over get_transactions, get_person_transactions, or the generic search, nor any exclusions.

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.