Dayze — Life Context

Attach Asset

attach_asset

Attach an asset_id to one of your entities. An asset uploaded without an entity is attached as is; one already on an entity gets a linked copy (the original row stays). Roles: original | processed | thumbnail | cover | document | receipt | certificate | other (photo is stored as original). Legacy: pass url instead of asset_id. ($0.10; API key required)

Input Schema

TableJSON Schema

Name	Required	Description
`url`	No	A web link (https://…) to an image. Not a storage path: upload a file, then attach its asset_id.
`role`	No	original \| cover \| thumbnail \| …
`asset_id`	No
`metadata`	No	Free-form metadata, merged into the stored metadata (metadata.source becomes the asset source).
`entity_id`	Yes
`asset_type`	No
`request_id`	No	Client idempotency key (retries return original result).
`description`	No	Caption for the attached asset (kept on a linked copy too).
`entity_type`	Yes
`idempotency_key`	No	Alias for request_id.

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
`asset_id`	No
`attached`	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"
+}

Changed1 schema field changedSep 30, 2026

addedInput schema / properties / url / description

Added value: +"A web link (https://…) to an image. Not a storage path: upload a file, then attach its asset_id."

Changed3 schema fields changedSep 30, 2026

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

addedInput schema / properties / description

Added value: +{
+  "description": "Caption for the attached asset (kept on a linked copy too).",
+  "type": "string"
+}

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

Changed5 schema fields changedSep 1, 2026
- addedInput schema / properties / asset_id
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / metadata
```
Added value: +{
+  "type": "object"
+}
```
- addedInput schema / properties / role
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / asset_id
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / attached
```
Added value: +{
+  "type": "boolean"
+}
```
AddedSep 1, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations declare it non-readonly and non-destructive, and the description adds real value beyond them: the linked-copy side effect ('the original row stays'), legacy url support, cost ($0.10), and an API key requirement. It stops short of rate limits or failure modes, so not a full 5.

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?

Purpose is front-loaded in the first sentence, followed by behavior, roles, legacy handling, and cost/auth. Dense single-paragraph packing, but nearly every clause earns its place; minor density cost keeps it from 5.

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?

For a mutation tool with an output schema (so return values need not be described) and annotations covering safety, the description supplies the essential remaining context: side effects, legacy path, and cost/auth. It is nearly complete, missing only idempotency/parameter nuances.

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 60% and the description mainly restates fields the schema already documents (roles list duplicates the enum, url legacy is also in the schema). It adds only the marginal note that 'photo is stored as original' and leaves metadata/request_id/idempotency_key unexplained in the description.

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 (attach an asset_id to an entity) and implicitly distinguishes itself from siblings like upload_asset (which creates an asset) by contrasting 'uploaded without an entity' vs 'already on an entity'. An agent can tell this links existing assets rather than creating them.

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?

Provides legacy usage context ('pass url instead of asset_id') and behavioral conditions (unattached vs already-attached), but never explicitly states when to use this over siblings such as upload_asset or update_asset. Usage is implied rather than routed.

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.