Dayze — Life Context

Log Food (diary write)

log_food

MUTATES the authenticated user Food Diary and calendar. Use when they ate or drank — do not store this as a chat memory. Supports dish_items for multiple named dishes with optional price and rating. Example: “I had Mee Pok for late lunch with my parents” → log_food({ what: "Mee Pok", kind: "meal", meal_period: "late lunch", with: ["my parents"] }). Optional: calories (user-stated kilocalories), place/merchant, amount, consumed_at (ISO). Explicit calories override the automatic heuristic. Resolves with/Mum/Dad via person aliases; unknown names do not fail the food write. Tags companions on the mirrored event. Rebuilds life_state. Requires API key or OAuth with scope context. Share tokens cannot write. ($0.10; API key required)

Input Schema

Name	Required	Description
`kind`	No
`what`	Yes	What they ate or drank (required). Example: Mee Pok
`with`	No	Companion names, aliases, ids, or group tokens. "my parents" / Mum / Dad resolve via aliases; "family" expands to CRM rows with family relationship labels
`notes`	No
`place`	No	Venue or location
`amount`	No	Price if mentioned
`paid_by`	No	Who paid. A person's name or alias for a third party; "self" / "me" = the user paid (recorded in Finance); "unknown" = payer not known. Not a payment method: use payment_method
`calories`	No	Kilocalories explicitly stated by the user; overrides the automatic heuristic and is stored with user provenance
`currency`	No	ISO currency, e.g. SGD
`merchant`	No	Restaurant, stall, or shop
`dish_items`	No	Ordered dishes in this entry. Each requires name; price and rating are optional.
`expense_id`	No	Link this entry to ONE existing Finance transaction you own (UUID from get_expenses / log_expense) instead of recording a new one
`person_ids`	No	Owned person UUIDs to tag (user-scoped)
`request_id`	No	Client idempotency key (retries return original result).
`consumed_at`	No	ISO instant; wins over meal_period
`meal_period`	No	Spoken period when consumed_at is omitted, e.g. "late lunch"
`people_names`	No	Alias for with
`payment_method`	No	How it was paid (cash, card, PayLah, PayNow…). Saved on the Finance transaction; never the payer
`idempotency_key`	No	Alias for request_id.

Output Schema

Name	Required	Description
`account`	No	The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
`food_id`	Yes
`message`	Yes
`event_id`	Yes
`food_log`	Yes	Saved Food Diary row.
`provenance`	No	Which connector wrote the record and which connected Dayze account received it.
`request_id`	No	The request key used for exact replay of this food write.
`inspect_url`	No	The Dayze page that shows the saved record.
`inspect_note`	No	What inspect_url opens. Never quote the record id.
`people_tagged`	Yes
`unresolved_people`	Yes
`life_state_rebuilt`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 21, 2026

addedOutput schema / properties / inspect_note

Added value: +{
+  "description": "What inspect_url opens. Never quote the record id.",
+  "type": "string"
+}

addedOutput schema / properties / inspect_url

Added value: +{
+  "description": "The Dayze page that shows the saved record.",
+  "type": "string"
+}

Changed3 schema fields changedOct 14, 2026

addedInput schema / properties / expense_id

Added value: +{
+  "description": "Link this entry to ONE existing Finance transaction you own (UUID from get_expenses / log_expense) instead of recording a new one",
+  "type": "string"
+}

changedInput schema / properties / paid_by / description

Previous value: -"Who paid (name or alias)"New value: +"Who paid. A person's name or alias for a third party; \"self\" / \"me\" = the user paid (recorded in Finance); \"unknown\" = payer not known. Not a payment method: use payment_method"

addedInput schema / properties / payment_method

Added value: +{
+  "description": "How it was paid (cash, card, PayLah, PayNow…). Saved on the Finance transaction; never the payer",
+  "type": "string"
+}

Changed1 schema field changedOct 6, 2026

addedOutput schema / properties / request_id

Added value: +{
+  "description": "The request key used for exact replay of this food write.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

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

Changed1 schema field changedSep 26, 2026

addedInput schema / properties / dish_items

Added value: +{
+  "description": "Ordered dishes in this entry. Each requires name; price and rating are optional.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "name": {
+        "type": "string"
+      },
+      "price": {
+        "minimum": 0,
+        "type": "number"
+      },
+      "rating": {
+        "maximum": 5,
+        "minimum": 1,
+        "type": "number"
+      }
+    },
+    "required": [
+      "name"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

Changed1 schema field changedSep 26, 2026

addedInput schema / properties / calories

Added value: +{
+  "description": "Kilocalories explicitly stated by the user; overrides the automatic heuristic and is stored with user provenance",
+  "maximum": 10000,
+  "minimum": 0,
+  "type": "number"
+}

Changed1 schema field changedSep 24, 2026

changedInput schema / properties / consumed_at / description

Previous value: -"ISO 8601 datetime; wins over meal_period"New value: +"ISO instant; wins over meal_period"

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

Changed1 schema field changedAug 31, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "event_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "food_id": {
+      "type": "string"
+    },
+    "food_log": {
+      "additionalProperties": true,
+      "description": "Saved Food Diary row.",
+      "type": "object"
+    },
+    "life_state_rebuilt": {
+      "type": "boolean"
+    },
+    "message": {
+      "type": "string"
+    },
+    "people_tagged": {
+      "items": {
+        "additionalProperties": true,
+        "description": "A Dayze person or contact record.",
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "unresolved_people": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "food_id",
+    "event_id",
+    "people_tagged",
+    "unresolved_people",
+    "food_log",
+    "message",
+    "life_state_rebuilt"
+  ],
+  "type": "object"
+}

Changed1 schema field changedAug 31, 2026

changedInput schema / properties / with / description

Previous value: -"Companion names, aliases, or ids. \"my parents\" / Mum / Dad resolve via aliases"New value: +"Companion names, aliases, ids, or group tokens. \"my parents\" / Mum / Dad resolve via aliases; \"family\" expands to CRM rows with family relationship labels"

AddedAug 29, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only say it is a non-read-only, non-destructive write. The description goes well beyond that: it discloses side effects (mirrors a calendar event, rebuilds life_state), alias-resolution behavior with graceful failure on unknown names, auth requirements (API key or OAuth scope context; share tokens cannot write), and cost ($0.10). This is exactly the extra context annotations cannot carry.

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?

Front-loads the mutation warning and trigger condition, then a worked example, then optional details. Dense but every sentence carries information; a few items (calories override, alias resolution) duplicate the schema, costing a point.

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

Completeness5/5

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

With an output schema present, return values need no explanation, and the description still covers auth, side effects, idempotency, and the explicit-calorie override. For a 19-parameter write tool at 89% schema coverage, nothing an agent needs to call it correctly is missing.

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 schema already documents nearly every parameter, including the calories-override and with/alias behavior the description repeats. The description adds a little (dish_items semantics for multiple named dishes), but mostly restates structured fields, so baseline 3 is appropriate.

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?

States a specific verb+resource ("MUTATES the authenticated user Food Diary and calendar") and clearly scopes it to eating/drinking records. An agent can distinguish it from siblings like log_expense, log_event, or log_interaction without opening a schema.

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?

Explicit when-to-use ("Use when they ate or drank") plus an explicit exclusion ("do not store this as a chat memory"). It does not, however, name a sibling alternative for overlapping cases (e.g., expense-only logging via log_expense), so routing between near-neighbors is left partly to inference.

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

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.