Dayze — Life Context

Get Transactions

get_transactions

Read-only

List individual expense/income/transfer rows (includes tags, payment_method). Requires context.read and financial_details:read. Filter with tag=project:… or project=… ($0.10; API key required)

Input Schema

TableJSON Schema

Name	Required	Description
`to`	No
`tag`	No	Exact tag, e.g. project:max-soko-poker-venture or rail:zelle
`from`	No
`type`	No
`limit`	No	Page size 1-500, default 100.
`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	Project label or slug → project:{slug}
`include_archived`	No

Output Schema

TableJSON Schema

Name	Required	Description
`count`	Yes
`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"
+}
```

Changed6 schema fields changedSep 13, 2026

addedInput schema / properties / from
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / limit
```
Added value: +{
+  "type": "number"
+}
```

addedInput schema / properties / project

Added value: +{
+  "description": "Project label or slug → project:{slug}",
+  "type": "string"
+}

addedInput schema / properties / tag

Added value: +{
+  "description": "Exact tag, e.g. project:max-soko-poker-venture or rail:zelle",
+  "type": "string"
+}

addedInput schema / properties / to
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / type
```
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?

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: required scopes (context.read, financial_details:read), an API-key requirement, and a $0.10 cost per call.

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?

Compact and front-loaded: the core resource is named first, then auth/cost constraints. Parenthetical asides add minor clutter but every clause carries information; no filler sentences.

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-format explanation is unnecessary. Auth requirements, cost, and key filtering patterns are covered, which is the important missing context for a costed, permission-gated read tool. The remaining gap is routing guidance versus sibling list/search tools.

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 coverage is 56%, and the schema itself documents tag, project, limit, and cursor semantics in more detail than the description. The description only adds the tag/project filter equivalence, which largely restates what the schema says, so it does not fully compensate for the uncovered parameters (from, to, type, include_archived).

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 and resource with scope: 'List individual expense/income/transfer rows', plus the returned fields (tags, payment_method). It is clear what the tool returns, though it never distinguishes itself from close siblings like get_expenses, get_person_transactions, or search_transactions.

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?

It gives a prerequisite and filter hint ('Requires context.read and financial_details:read. Filter with tag=project:… or project=…'), which implies usage context. But it offers no when-to-use/when-not guidance and never routes the agent to an alternative such as search_transactions versus a full listing.

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.