Dayze — Life Context

Record Sale

record_sale

Mark inventory sold + record sale proceeds with gain/loss. ($0.10; API key required)

Input Schema

TableJSON Schema

Name	Required	Description
`date`	No	Alias for sold_at.
`notes`	No
`amount`	Yes	Sale proceeds.
`sold_at`	No	YYYY-MM-DD; default today. Alias: date.
`currency`	No	ISO 4217; default USD.
`request_id`	No	Client idempotency key (retries return original result).
`marketplace`	No	Where it sold (the income row's merchant; default "sale").
`inventory_id`	Yes	The item sold (get_inventory / search_inventory).
`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.
`message`	No
`expense_id`	No
`provenance`	No	Which connector wrote the record and which connected Dayze account received it.
`inventory_id`	No
`realized_gain_loss`	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"
+}

Changed8 schema fields changedSep 30, 2026

changedInput schema / additionalProperties
```
Previous value: -trueNew value: +false
```
addedInput schema / properties / amount / description
```
Added value: +"Sale proceeds."
```
addedInput schema / properties / currency / description
```
Added value: +"ISO 4217; default USD."
```

addedInput schema / properties / date

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

addedInput schema / properties / inventory_id / description

Added value: +"The item sold (get_inventory / search_inventory)."

addedInput schema / properties / marketplace

Added value: +{
+  "description": "Where it sold (the income row's merchant; default \"sale\").",
+  "type": "string"
+}

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

addedInput schema / properties / sold_at / description

Added value: +"YYYY-MM-DD; default today. Alias: date."

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

AddedSep 1, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already establish the read-only/destructive profile, and the description adds two things structured data doesn't: a cost figure ($0.10) and an API-key requirement. It still omits that an income/merchant row is created and that retries are idempotent, but that is genuinely useful added context.

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?

A single front-loaded sentence with a compact parenthetical for cost and auth. Nothing wasted, though it is arguably too terse given the tool's complexity.

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?

Output schema exists, so return values need no explanation. However, for a 9-parameter mutation that links inventory to financial records, the description doesn't explain the side effects (inventory marked sold, income row created), idempotency, or prerequisites that an agent would want before calling.

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 89%, so the descriptions on inventory_id, amount, sold_at, currency, marketplace, and request_id already carry the meaning. The description itself contributes nothing about the 9 parameters, so the baseline 3 applies.

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 pair: marking an inventory item sold and recording sale proceeds with gain/loss. This distinguishes it from siblings like record_purchase or log_income, though it doesn't explicitly name those alternatives.

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?

The description gives no when-to-use guidance and never mentions alternatives such as record_purchase, log_income, or log_transaction. The only routing hint ('get_inventory / search_inventory') lives in the schema, not the description.

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.