Dayze — Life Context

Attach Food Photo (Food Diary photo)

attach_food_photo

MUTATES one Food Diary row the authenticated user owns by storing a meal photo on it (same pipeline as the web diary upload). Required: food_id (UUID from log_food / search) plus exactly one of image_base64 (raw base64 or data: URL) or url (public https image). JPEG, PNG, WebP, GIF, HEIC, or AVIF under 8 MB. One photo per entry: calling again replaces photo_url (replaced/previous_photo_url report it). EXIF capture time moves consumed_at unless keep_consumed_at=true. Unknown or other-user food_id returns not_found and stores nothing. Response photo_url is re-read from the row. Syncs the mirrored calendar event and rebuilds life_state. Requires API key or OAuth with scope context. Share tokens cannot write. ($0.15; API key required)

Input Schema

TableJSON Schema

Name	Required	Description
`url`	No	Public https image URL to fetch and store. Use this or image_base64.
`food_id`	Yes	UUID of a Food Diary row the authenticated user owns
`filename`	No	Optional original filename
`request_id`	No	Client idempotency key (retries return original result).
`image_base64`	No	Image bytes as base64 (optional data:image/...;base64, prefix). Use this or url.
`idempotency_key`	No	Alias for request_id.
`keep_consumed_at`	No	true keeps the entry time even if the photo EXIF has a capture time

Output Schema

TableJSON Schema

Name	Required	Description
`photo`	Yes	Stored image summary (mime_type, file_size_bytes, taken_at).
`account`	No	The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
`food_id`	Yes
`event_id`	Yes
`replaced`	Yes	True when the entry already had a photo.
`photo_url`	Yes	Stored photo URL, re-read from the Food Diary row.
`provenance`	No	Which connector wrote the record and which connected Dayze account received it.
`consumed_at`	Yes
`life_state_rebuilt`	Yes
`previous_photo_url`	Yes
`consumed_at_changed`	Yes	True when photo EXIF moved the entry time.

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

Changed1 schema field changedSep 30, 2026

changedInput schema / properties / url / description

Previous value: -"Public http(s) image URL to fetch and store. Use this or image_base64."New value: +"Public https image URL to fetch and store. Use this or image_base64."

AddedSep 26, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=false). It discloses one-photo-per-entry replacement semantics, that replaced URLs are reported, that EXIF capture time shifts consumed_at unless keep_consumed_at=true, that unknown/other-user food_id returns not_found and stores nothing, that the calendar event is synced and life_state rebuilt, auth requirements, and cost. This is rich, decision-relevant disclosure.

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?

The verb and scope are front-loaded in the first clause, and the dense remainder is largely load-bearing detail. It is a long single block, and the auth/cost/side-effect sentences could be tightened, but nothing is filler.

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 annotations, a 100%-covered schema, and an output schema present, the description covers the remaining gaps an agent needs: auth modes, share-token restriction, idempotency, replacement behavior, and side effects. Nothing material for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description meaningfully extends it: 'exactly one of' image_base64 or url, accepted formats (JPEG/PNG/WebP/GIF/HEIC/AVIF), and the 8 MB size cap -- none of which appear in the schema. It also explains the keep_consumed_at effect in narrative form.

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?

Opens with a specific verb+resource+scope: 'MUTATES one Food Diary row the authenticated user owns by storing a meal photo on it'. The parenthetical about the web diary upload pipeline and the food_id sourcing make it clearly distinct from generic upload_photo/attach_asset siblings. An agent can tell exactly what this does without opening the 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?

States the required food_id and names where to obtain it (log_food / search), which gives real routing context. It also clarifies the either/or between image_base64 and url. However, it never explicitly contrasts against the closest siblings (upload_photo, attach_asset, update_food), so there is no stated when-not.

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.