Dayze — Life Context

Log Income

log_income

Record money received (Stripe, refunds, payroll, Venmo). log_transaction with type income and direction from already set (pass neither). Use external_id for Stripe/Gmail idempotency. A contact paying back an IOU: category "IOU repayment" + person_id (lowers the IOU, shows the money once). A contact lending the user cash: category "IOU lend" + person_id (creates the IOU the user owes, shows the money 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
`project`	No	Venture/project label → stored as project:{slug} tag (e.g. Max Soko poker venture)
`category`	No	e.g. Salary, Gift, Refund. "IOU repayment" and "IOU lend" 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
`person_id`	No
`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
`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
`idempotency_key`	No	Alias for request_id.
`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"
+}

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

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

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

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: -"e.g. Salary, Gift, Refund. \"IOU repayment\" needs person_id."New value: +"e.g. Salary, Gift, Refund. \"IOU repayment\" and \"IOU lend\" need person_id."

Changed2 schema fields changedSep 30, 2026

addedInput schema / properties / category

Added value: +{
+  "description": "e.g. Salary, Gift, Refund. \"IOU repayment\" 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"
+}

Changed1 schema field changedSep 13, 2026
- addedOutput schema / properties / event_id
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
AddedSep 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations declare the safety profile (non-read-only, non-destructive), and the description adds context annotations don't carry: the $0.10 cost and API-key requirement, plus side effects ('lowers the IOU', 'creates the IOU the user owes', 'shows the money once'). It doesn't cover validation failures or duplicate handling in depth, but the IOU side-effect disclosure is genuinely valuable.

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 adds IOU nuance in compact parenthetical clauses. Dense but every sentence carries actionable content; the IOU pairing is slightly terse but not wasteful.

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 needn't be described, and the description covers the tricky IOU/idempotency semantics an agent must get right for a 20-param write tool. Minor gaps remain on the many peripheral params, but the critical decision logic is present.

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 only 60%, so the description must compensate, and it does for the highest-risk params: it ties category ('IOU repayment'/'IOU lend') to person_id, explains external_id for Stripe/Gmail idempotency, and clarifies the IOU flow. It leaves several params (source, merchant, currency, payment_method, tags) unexplained, keeping it short of a 5.

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+resource ('Record money received') and immediately lists concrete examples (Stripe, refunds, payroll, Venmo). It also explicitly differentiates itself from the sibling log_transaction by noting income/type and direction are pre-set, so an agent can route correctly without opening either schema.

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 clear when-to-use guidance with two worked scenarios (contact repaying an IOU vs. a contact lending cash), including which category and person_id to supply. It routes the generic case to log_transaction, though it doesn't state explicit exclusions for other income-like tools.

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.