Dayze — Life Context

Update Asset

update_asset

Patch role, metadata, description, or parent_asset_id (e.g. mark as processed). ($0.08; API key required)

Input Schema

TableJSON Schema

Name	Required	Description
`role`	No	original \| cover \| thumbnail \| …
`asset_id`	Yes
`filename`	No
`metadata`	No	Free-form metadata, merged into the stored metadata (metadata.source becomes the asset source).
`asset_type`	No
`request_id`	No	Client idempotency key (retries return original result).
`description`	No
`idempotency_key`	No	Alias for request_id.
`parent_asset_id`	No

Output Schema

TableJSON Schema

Name	Required	Description
`asset`	No
`account`	No	The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
`message`	No
`updated`	No
`asset_id`	No
`provenance`	No	Which connector wrote the record and which connected Dayze account received it.

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

Changed2 schema fields changedSep 30, 2026

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

addedInput schema / properties / metadata / description

Added value: +"Free-form metadata, merged into the stored metadata (metadata.source becomes the asset source)."

Changed1 schema field changedSep 11, 2026

changedInput schema / properties / role / enum

Previous value: -[
-  "original",
-  "processed",
-  "thumbnail",
-  "cover",
-  "document",
-  "receipt",
-  "certificate",
-  "other"
-]New value: +[
+  "original",
+  "processed",
+  "thumbnail",
+  "cover",
+  "document",
+  "receipt",
+  "certificate",
+  "photo",
+  "other"
+]

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

Changed2 schema fields changedSep 1, 2026

addedInput schema / properties / role / description

Added value: +"original | cover | thumbnail | …"

addedInput schema / properties / role / enum

Added value: +[
+  "original",
+  "processed",
+  "thumbnail",
+  "cover",
+  "document",
+  "receipt",
+  "certificate",
+  "other"
+]

AddedSep 1, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so safety is covered; the description adds valuable non-annotation context in the form of cost ($0.08) and an auth requirement (API key). It does not, however, explain partial-patch merge semantics for unspecified fields.

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?

A single tight sentence leads with the action and fields, with the cost/auth caveat parenthetically appended. No filler; every clause earns its place.

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?

An output schema exists so return values needn't be explained, but for a 9-parameter mutation tool with 44% schema coverage the description is thin, omitting filename/asset_type semantics and any note on merge behavior for metadata.

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 44%, so the description must carry more weight, yet it names just 4 of 9 parameters (role, metadata, description, parent_asset_id) and says nothing about filename or asset_type. It adds the 'mark as processed' role hint, but leaves the coverage gap only partly filled.

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 ('Patch') and resource ('asset') and enumerates the mutable fields (role, metadata, description, parent_asset_id), which distinguishes it from sibling reads like get_asset and creation tools like upload_asset/attach_asset. It stops short of explicitly naming which sibling it is not.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The example '(e.g. mark as processed)' gives a concrete scenario, implying when to reach for it, but there is no explicit guidance on when to prefer alternatives such as archive_asset or attach_asset, and no exclusions or prerequisites.

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.