Dayze — Life Context

Log Transaction

log_transaction

Income/expense/transfer write. direction=from + type=income for Venmo/Stripe/refunds received. Positive amount; external_id dedupes imports. Optional project/tags. Zelle always USD. Optional mirror_event creates a calendar Money · annotation (ledger is still the source of truth for /money). IOU repayment ("Mark paid me back $200"): category "IOU repayment" + person_id — one call lowers the IOU and shows the money once (direction from = they paid the user, to = the user paid them). A cash loan ("I lent Mark $200"): category "IOU lend" + person_id — one call creates the IOU and shows the money once on that day (direction to = the user lent them, from = they lent the user); cash_moved: false for an owed share (IOU only). A plain income from a contact with an open IOU is refused unless not_iou_repayment: true; the same money as an already-recorded repayment or loan comes back as duplicate. ($0.10; API key required)

Input Schema

TableJSON Schema

Name	Required	Description
`date`	No
`tags`	No	Optional tags. Prefer project: / ext: / rail: grammar.
`type`	No
`notes`	No	Free text about the payment. Alias: description.
`amount`	Yes
`source`	No
`project`	No	Venture/project label → stored as project:{slug} tag (e.g. Max Soko poker venture)
`category`	No	Ledger category (e.g. Salary, Gift, Refund, Transfer in, Food & Dining). "IOU repayment" = a contact paying back a loan IOU; "IOU lend" = a cash loan; "Invoice payment" = collecting an unpaid invoice (need person_id).
`currency`	No
`iou_type`	No	loan (default) or invoice. Invoice = unpaid receivable: no Finance outflow on create; payment is income "Invoice payment". Use for invoice/receivable phrasings; "I lent…" → loan.
`merchant`	No
`direction`	Yes
`person_id`	No
`account_id`	No	Stable provider account identity for imported payments.
`cash_moved`	No	With category "IOU lend": true (default) = cash changed hands as a loan (shows in Finance); false = an owed share, e.g. of a dinner logged as its own expense (IOU only). Ignored for iou_type invoice.
`message_id`	No
`request_id`	No	Client idempotency key (retries return original result).
`description`	No	Alias for notes.
`external_id`	No
`person_name`	No	The contact by name, when there is no person_id (IOU categories need one or the other).
`client_label`	No	Optional free-text client label for an invoice IOU.
`mirror_event`	No	Also insert optional Money · calendar event (default false)
`payment_method`	No
`idempotency_key`	No	Alias for request_id.
`extractor_version`	No
`not_iou_repayment`	No	true only when income from a contact with an open IOU is unrelated to it.

Output Schema

TableJSON Schema

Name	Required	Description
`type`	No
`account`	No	The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
`message`	No
`event_id`	No
`direction`	No
`duplicate`	No
`expense_id`	No
`provenance`	No	Which connector wrote the record and which connected Dayze account received it.
`transaction`	No	Expense/income transaction row.
`transaction_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 3, 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 / provenance

Added value: +{
+  "additionalProperties": false,
+  "description": "Which connector wrote the record and which connected Dayze account received it.",
+  "properties": {
+    "account": {
+      "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"
+    },
+    "channel": {
+      "description": "Always mcp_connector.",
+      "type": "string"
+    },
+    "connector": {
+      "additionalProperties": false,
+      "properties": {
+        "kind": {
+          "description": "oauth or api_key.",
+          "type": "string"
+        },
+        "name": {
+          "description": "The connected app or API-key label shown to the account owner.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "kind",
+        "name"
+      ],
+      "type": "object"
+    },
+    "source": {
+      "description": "chatgpt for ChatGPT OAuth writes; mcp for another OAuth app or API key.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "source",
+    "channel",
+    "connector",
+    "account"
+  ],
+  "type": "object"
+}

Changed4 schema fields changedOct 3, 2026

changedInput schema / properties / cash_moved / description

Previous value: -"With category \"IOU lend\": true (default) = cash changed hands as a loan (shows in Finance); false = an owed share, e.g. of a dinner logged as its own expense (IOU only)."New value: +"With category \"IOU lend\": true (default) = cash changed hands as a loan (shows in Finance); false = an owed share, e.g. of a dinner logged as its own expense (IOU only). Ignored for iou_type invoice."

changedInput schema / properties / category / description

Previous value: -"Ledger category (e.g. Salary, Gift, Refund, Transfer in, Food & Dining). \"IOU repayment\" = a contact paying back an IOU; \"IOU lend\" = a cash loan to or from a contact (both need person_id)."New value: +"Ledger category (e.g. Salary, Gift, Refund, Transfer in, Food & Dining). \"IOU repayment\" = a contact paying back a loan IOU; \"IOU lend\" = a cash loan; \"Invoice payment\" = collecting an unpaid invoice (need person_id)."

addedInput schema / properties / client_label

Added value: +{
+  "description": "Optional free-text client label for an invoice IOU.",
+  "type": "string"
+}

addedInput schema / properties / iou_type

Added value: +{
+  "description": "loan (default) or invoice. Invoice = unpaid receivable: no Finance outflow on create; payment is income \"Invoice payment\". Use for invoice/receivable phrasings; \"I lent…\" → loan.",
+  "type": "string"
+}

Changed4 schema fields changedSep 30, 2026

changedInput schema / additionalProperties
```
Previous value: -trueNew value: +false
```

addedInput schema / properties / description

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

addedInput schema / properties / notes / description

Added value: +"Free text about the payment. Alias: description."

addedInput schema / properties / person_name

Added value: +{
+  "description": "The contact by name, when there is no person_id (IOU categories need one or the other).",
+  "type": "string"
+}

Changed2 schema fields changedSep 30, 2026

addedInput schema / properties / cash_moved

Added value: +{
+  "description": "With category \"IOU lend\": true (default) = cash changed hands as a loan (shows in Finance); false = an owed share, e.g. of a dinner logged as its own expense (IOU only).",
+  "type": "boolean"
+}

changedInput schema / properties / category / description

Previous value: -"Ledger category (e.g. Salary, Gift, Refund, Transfer in, Food & Dining). \"IOU repayment\" = a contact paying back an IOU (needs person_id)."New value: +"Ledger category (e.g. Salary, Gift, Refund, Transfer in, Food & Dining). \"IOU repayment\" = a contact paying back an IOU; \"IOU lend\" = a cash loan to or from a contact (both need person_id)."

Changed2 schema fields changedSep 30, 2026

addedInput schema / properties / category

Added value: +{
+  "description": "Ledger category (e.g. Salary, Gift, Refund, Transfer in, Food & Dining). \"IOU repayment\" = a contact paying back an IOU (needs person_id).",
+  "type": "string"
+}

addedInput schema / properties / not_iou_repayment

Added value: +{
+  "description": "true only when income from a contact with an open IOU is unrelated to it.",
+  "type": "boolean"
+}

Changed3 schema fields changedSep 16, 2026

addedInput schema / properties / account_id

Added value: +{
+  "description": "Stable provider account identity for imported payments.",
+  "type": "string"
+}

addedInput schema / properties / extractor_version
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / message_id
```
Added value: +{
+  "type": "string"
+}
```

Changed2 schema fields changedSep 13, 2026

addedInput schema / properties / mirror_event

Added value: +{
+  "description": "Also insert optional Money · calendar event (default false)",
+  "type": "boolean"
+}

addedOutput schema / properties / event_id

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed2 schema fields changedSep 13, 2026

addedInput schema / properties / project

Added value: +{
+  "description": "Venture/project label → stored as project:{slug} tag (e.g. Max Soko poker venture)",
+  "type": "string"
+}

addedInput schema / properties / tags

Added value: +{
+  "description": "Optional tags. Prefer project: / ext: / rail: grammar.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed1 schema field changedSep 10, 2026
- addedInput schema / properties / payment_method
```
Added value: +{
+  "type": "string"
+}
```

Changed2 schema fields changedSep 4, 2026

addedInput schema / properties / idempotency_key

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

addedInput schema / properties / request_id

Added value: +{
+  "description": "Client idempotency key (retries return original result).",
+  "type": "string"
+}

Changed3 schema fields changedSep 2, 2026

addedInput schema / properties / merchant
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / notes
```
Added value: +{
+  "type": "string"
+}
```

changedInput schema / required

Previous value: -[
-  "amount"
-]New value: +[
+  "amount",
+  "direction"
+]

AddedSep 2, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Annotations only declare it is a non-destructive write; the description adds substantial behavior beyond that: per-call cost ($0.10) and API-key requirement, external_id dedupe for imports, request_id/idempotency_key retry semantics, the refusal of plain income from a contact with an open IOU, duplicate detection for already-recorded repayments, and the mirror_event side effect with the ledger remaining source of truth.

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?

Purpose and cost are front-loaded, and each subsequent clause encodes a distinct business rule rather than filler. It is dense and reads as a run-on, but given the 26-parameter surface the length is largely earned.

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 not be described. The description covers the tricky IOU/loan/invoice flows, cost, auth and idempotency, leaving only minor gaps such as currency/Zelle and transfer-type specifics relative to the parameter set.

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?

With 26 params and only 54% schema coverage, the description carries real weight: it explains direction semantics for IOU cases, positive-amount convention, external_id dedupe, optional project/tags, category values ('IOU repayment', 'IOU lend'), cash_moved=true/false meaning, and not_iou_repayment. This meaningfully compensates for the undocumented half of the schema.

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?

Opens with 'Income/expense/transfer write,' a specific verb plus resource that tells the agent this records money movements across all three types. It does not, however, distinguish itself from siblings like log_income, log_expense, record_purchase or record_sale, so the agent cannot tell from the text alone why it should pick this tool over those.

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 concrete when-to-use routing for real scenarios: 'direction=from + type=income for Venmo/Stripe/refunds received', IOU repayment via category+person_id, cash loan via 'IOU lend', and the refusal condition requiring not_iou_repayment. It stops short of naming alternatives or exclusions against the log_income/log_expense siblings.

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.