Dayze — Life Context

Record Purchase

record_purchase

Atomic expense + optional inventory item creation. ($0.10; API key required)

Input Schema

TableJSON Schema

Name	Required	Description
`date`	No	YYYY-MM-DD; default today.
`name`	Yes	What was bought (also the Inventory item name). Alias: merchant.
`amount`	Yes
`category`	No	Expense category (default purchase); also the item category when inventory_details has none.
`currency`	No	ISO 4217; default USD.
`merchant`	No	Where it was bought; stands in for name when name is missing.
`request_id`	No	Client idempotency key (retries return original result).
`idempotency_key`	No	Alias for request_id.
`create_inventory`	No	false = the expense only, no Inventory item (default true).
`inventory_details`	No	The Inventory item: category, brand, model, condition, notes.

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.
`transaction`	No	Expense/income transaction row.
`inventory_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"
+}

Changed8 schema fields changedSep 30, 2026

changedInput schema / additionalProperties
```
Previous value: -trueNew value: +false
```

addedInput schema / properties / category

Added value: +{
+  "description": "Expense category (default purchase); also the item category when inventory_details has none.",
+  "type": "string"
+}

addedInput schema / properties / create_inventory

Added value: +{
+  "description": "false = the expense only, no Inventory item (default true).",
+  "type": "boolean"
+}

addedInput schema / properties / currency / description
```
Added value: +"ISO 4217; default USD."
```
addedInput schema / properties / date / description
```
Added value: +"YYYY-MM-DD; default today."
```

addedInput schema / properties / inventory_details

Added value: +{
+  "additionalProperties": false,
+  "description": "The Inventory item: category, brand, model, condition, notes.",
+  "properties": {
+    "brand": {
+      "type": "string"
+    },
+    "category": {
+      "type": "string"
+    },
+    "condition": {
+      "enum": [
+        "new",
+        "excellent",
+        "good",
+        "worn",
+        "needs_repair",
+        "retired"
+      ],
+      "type": "string"
+    },
+    "model": {
+      "type": "string"
+    },
+    "notes": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedInput schema / properties / merchant

Added value: +{
+  "description": "Where it was bought; stands in for name when name is missing.",
+  "type": "string"
+}

addedInput schema / properties / name / description

Added value: +"What was bought (also the Inventory item name). Alias: merchant."

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

A3.6/5.0

Behavior4/5

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

Annotations cover the safety profile (not read-only, non-destructive, closed-world), and the description adds genuinely non-structured context: the operation is atomic, costs $0.10, and requires an API key. No failure modes or rollback behavior are described, so it stops short of a 5.

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?

Two compact clauses, front-loaded with the core capability and immediately followed by cost and auth requirements. Nothing is wasted and no sentence is filler.

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 10 parameters, a nested object, and an output schema, the description's job is mainly routing and cost/auth context, which it delivers. The one gap is that it does not indicate what happens when create_inventory=true and inventory creation fails after the expense is written, a meaningful concern for an 'atomic' claim.

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 90%, so the schema already documents name/merchant aliasing, currency defaults, idempotency keys, and the nested inventory_details fields. The description adds only the high-level existence of the optional inventory item, which the schema covers in more detail. Baseline 3 is appropriate.

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 ('expense + optional inventory item creation') plus the atomic coordination between them, which distinguishes it from simple single-resource loggers. However it never names the sibling tools (log_expense, add_inventory_item) it overlaps with, so the agent must infer the boundary from the sibling list alone.

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 is given: nothing says to prefer this over log_expense when inventory is not needed, or over add_inventory_item when no expense results. The only hint is 'optional inventory item creation', which leaves the selection criteria implicit.

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.