Dayze — Life Context

Log Expense

log_expense

Create an outgoing expense only. For money received (Venmo/Cash App/PayPal/Zelle) use log_transaction with direction=from and type=income. Lending a contact cash: category "IOU lend" + person_id (one call creates the IOU they owe and shows the money out once). ($0.10; API key required)

Input Schema

TableJSON Schema

Name	Required	Description
`date`	No
`tags`	No	Optional tags. Prefer project: / ext: / rail: grammar.
`notes`	No	Free text about the payment. Alias: description.
`amount`	Yes
`source`	No	Payment rail or app: venmo, zelle, cashapp, card, cash, … Alias: payment_method.
`project`	No	Venture/project label → stored as project:{slug} tag (e.g. Max Soko poker venture)
`category`	No	"IOU repayment" = paying a contact back; "IOU lend" = lending a contact cash (both 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	Payee name (defaults when omitted)
`person_id`	No	The contact paid (needed for "IOU repayment" / "IOU lend").
`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.
`request_id`	No	Client idempotency key (retries return original result).
`description`	No	Alias for notes.
`external_id`	No	The provider's id for this payment; dedupes imports. Without a request_id it is required.
`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.
`payment_method`	No	Alias for source.
`idempotency_key`	No	Alias for request_id.

Output Schema

TableJSON Schema

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

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

Changed3 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."

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

Changed9 schema fields changedSep 30, 2026

changedInput schema / additionalProperties
```
Previous value: -trueNew value: +false
```
addedInput schema / properties / description / description
```
Added value: +"Alias for notes."
```

addedInput schema / properties / external_id

Added value: +{
+  "description": "The provider's id for this payment; dedupes imports. Without a request_id it is required.",
+  "type": "string"
+}

addedInput schema / properties / notes / description

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

addedInput schema / properties / payment_method

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

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

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 / source

Added value: +{
+  "description": "Payment rail or app: venmo, zelle, cashapp, card, cash, … Alias: payment_method.",
+  "type": "string"
+}

addedInput schema / properties / tags

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

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

addedInput schema / properties / category / description

Added value: +"\"IOU repayment\" = paying a contact back; \"IOU lend\" = lending a contact cash (both need person_id)."

addedInput schema / properties / person_id

Added value: +{
+  "description": "The contact paid (needed for \"IOU repayment\" / \"IOU lend\").",
+  "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"
+}

Changed4 schema fields changedSep 1, 2026

addedInput schema / properties / category
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / description
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / merchant

Added value: +{
+  "description": "Payee name (defaults when omitted)",
+  "type": "string"
+}

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

AddedSep 1, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations declare a non-destructive write with no open-world access. The description goes beyond them by disclosing cost ($0.10), an auth requirement (API key), and the important side effect that one "IOU lend" call creates the receivable and records the outflow simultaneously. It stops short of describing what the response returns, but the added operational context is substantial.

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?

Front-loads the core purpose, then alternatives, then the special IOU case, then cost/auth as a trailing parenthetical. Every sentence carries distinct information, though the IOU sentence is dense and could be unpacked slightly.

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?

With an output schema present, return values need no explanation, and the description covers the main outgoing, income-alternative, and IOU flows. Given 19 parameters and the write semantics, the definition is largely sufficient, though it says nothing about the many IOU/invoice-related fields beyond the one lending case.

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 84%, so the schema already carries most parameter meaning. The description adds cross-parameter semantics by tying category "IOU lend" to person_id and explaining the single-call IOU effect, which is value beyond the per-field descriptions, but this only touches a couple of the 19 parameters.

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?

States a specific verb and resource ("Create an outgoing expense") and immediately bounds scope with "only," which distinguishes it from log_income and the general log_transaction. An agent can tell which tool to reach for without opening any schema.

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 routes the wrong-case to an alternative ("For money received ... use log_transaction with direction=from and type=income") and names the exact parameters to use. It also describes the lending-contact case with the required category/person_id combination, so the when-to-use and when-not-to-use conditions are both covered.

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.