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
`notes`	No
`amount`	No
`source`	No	Alias of payment_method
`category`	No
`currency`	No
`merchant`	No
`expense_id`	Yes
`request_id`	No	Client idempotency key (retries return original result).
`description`	No
`payment_method`	No	e.g. venmo, cash, card
`idempotency_key`	No	Alias for request_id.

Output Schema

TableJSON Schema

Name	Required	Description
`changed`	No
`expense`	No	Expense/income transaction row.
`message`	No

Schema Changelog

Changes observed during successful MCP inspections.

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

A3.8/5.0

Behavior4/5

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

With annotations already indicating that this is a write operation (readOnlyHint=false) and not destructive, the description adds value beyond them by specifying the HTTP method 'PATCH', which implies partial update semantics. It also discloses authentication needs (API key) and cost ($0.10), which are not present in the annotations. It does not contradict the annotations.

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

Conciseness5/5

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

The description is a single, front-loaded sentence with zero filler. 'PATCH an expense row' immediately conveys the core action, and the parenthetical compactly adds essential operational details about cost and authorization. Every part earns its place.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is minimally viable: it names the operation, implies mutation of an existing expense, and includes key operational constraints. The input schema supplies property names and types, and an output schema exists so return values need not be described. However, for a 12-parameter write tool, the description lacks guidance on field semantics, partial-update behavior, and when to prefer log_expense, leaving clear gaps.

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?

The description provides no parameter-level meaning or guidance. Schema coverage is only 42%, and several parameters such as expense_id, amount, category, currency, merchant, and notes lack descriptions. The schema does describe some ambiguous fields like date and request_id, but the description itself does not compensate for the low coverage.

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?

The description states a concrete operation: 'PATCH an expense row.' This is a specific verb plus resource, clearly distinguishing it from read tools like get_expenses and creation tools like log_expense. The HTTP verb 'PATCH' also communicates that this updates an existing expense rather than creating a new one.

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?

The description implies usage for updating an existing expense row via 'PATCH', and it provides operational prerequisites: cost and API key requirement. However, it does not explicitly state when to use this tool versus log_expense or other update tools, nor mention that expense_id must identify an existing row. Usage context is implied rather than made explicit.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.