Dayze — Life Context

Update Expense

update_expense

PATCH an expense row. ($0.10; API key required)

Input Schema

TableJSON Schema

Name	Required	Description
`date`	No	YYYY-MM-DD expense_date
`tags`	No
`notes`	No
`amount`	No
`source`	No	Alias of payment_method
`project`	No	Venture label → project:{slug} tag
`category`	No
`currency`	No
`merchant`	No
`expense_id`	Yes
`request_id`	No	Client idempotency key (retries return original result).
`description`	No
`external_id`	No	Optional; merges ext:{source}:{id} into tags
`payment_method`	No	e.g. venmo, cash, card
`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.
`changed`	No
`expense`	No	Expense/income transaction row.
`message`	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 changedSep 13, 2026

addedInput schema / properties / external_id

Added value: +{
+  "description": "Optional; merges ext:{source}:{id} into tags",
+  "type": "string"
+}

addedInput schema / properties / project

Added value: +{
+  "description": "Venture label → project:{slug} tag",
+  "type": "string"
+}

addedInput schema / properties / tags

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed4 schema fields changedSep 11, 2026

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

addedInput schema / properties / payment_method

Added value: +{
+  "description": "e.g. venmo, cash, card",
+  "type": "string"
+}

addedInput schema / properties / source

Added value: +{
+  "description": "Alias of payment_method",
+  "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"
+}

Changed6 schema fields changedSep 1, 2026

changedInput schema / additionalProperties
```
Previous value: -trueNew value: +false
```
addedInput schema / properties / amount
```
Added value: +{
+  "type": "number"
+}
```
addedInput schema / properties / category
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / date

Added value: +{
+  "description": "YYYY-MM-DD expense_date",
+  "type": "string"
+}

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

AddedSep 1, 2026

TDQS

C2.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context — a $0.10 per-call cost and an API key requirement — but says nothing about partial-update semantics or whether omitted fields are preserved.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short fragments with the operation front-loaded and zero waste. However, the brevity comes at the cost of substance for a 15-parameter mutation tool, so it reads as under-specified rather than efficiently concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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. But for a 15-parameter mutation tool at 47% schema coverage, the agent still lacks the field-level and partial-update guidance needed to call it correctly, leaving the definition materially incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 47% and the description names no parameter behavior at all, so it does not compensate for the gap. Fields like tags, notes, amount, category, currency, merchant, and description are undocumented in both places, and the PATCH/partial-update contract is never explained.

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+resource ('PATCH an expense row'), so an agent knows this mutates an existing expense. It does not differentiate from closely related siblings such as log_expense, archive_expense, or restore_expense, leaving the agent to infer the boundary. Clear but not sibling-aware.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance, no alternatives, and no exclusions. With siblings like log_expense (create), archive_expense (soft-delete), and restore_expense nearby, an agent gets no routing help for choosing update_expense over them.

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.