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. Prefer this (or log_income) over log_expense for money received. ($0.10; API key required)

Input Schema

TableJSON Schema

Name	Required	Description
`date`	No
`type`	No
`notes`	No
`amount`	Yes
`source`	No
`currency`	No
`merchant`	No
`direction`	Yes
`person_id`	No
`request_id`	No	Client idempotency key (retries return original result).
`external_id`	No
`payment_method`	No
`idempotency_key`	No	Alias for request_id.

Output Schema

TableJSON Schema

Name	Required	Description
`type`	No
`message`	No
`direction`	No
`duplicate`	No
`expense_id`	No
`transaction`	No	Expense/income transaction row.
`transaction_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

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

Behavior4/5

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

Annotations already show this is a write (readOnlyHint=false) but the description adds important behavioral detail: it requires an API key, costs $0.10, requires positive amounts, and uses external_id to dedupe imports. No contradiction exists between the description and 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?

Four short sentences deliver purpose, usage guidance, a deduplication caveat, and cost/API requirement with no fluff. The most important information is front-loaded.

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?

For a 13-parameter write operation, the description covers the essential invocation constraints and trade-offs, and an output schema exists for return values. It does not explain how to handle transfer direction or undocumented parameters, so it is strong but not exhaustive.

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 coverage is only 15%, and the description compensates for key parameters by explaining the direction/type combination, positive amount constraint, and external_id deduplication semantics. However, many other fields (date, merchant, person_id, payment_method, etc.) remain undocumented by both schema and description, leaving a notable gap.

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?

Starts with a precise verb-resource phrase ('Income/expense/transfer write') that immediately identifies the operationy and the target. It also differentiates the tool from siblings by explicitly stating it should be preferred over log_expense for money received, and names log_income as an acceptable alternative.

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 conditions for use: direction=from plus type=income for Venmo/Stripe/refunds, and tells the agent to prefer this tool (or log_income) over log_expense when money is received. It also states cost and API key requirement, but does not fully specify when to choose log_income instead of log_transaction.

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.