Dayze — Life Context

Log Favorite Song (music write)

log_favorite_song

MUTATES the authenticated user favorite tracks list at /music. Use when they favorite or save a song — do not store this as a chat memory or in music_preferences. Example: “Henry Mancini - Piano And Strings (1995 Remastered)” → log_favorite_song({ track: "Henry Mancini - Piano And Strings (1995 Remastered)" }) or title + artist. Optional year_note, source_url, and person_id from get_people to link the track to one owned contact. Requires API key or OAuth with scope context. Share tokens cannot write. ($0.10; API key required)

Input Schema

Name	Required	Description
`url`	No	Alias for source_url
`title`	No	Track title (required unless track blob parses)
`track`	No	Optional "Artist - Title (year remaster)" blob
`artist`	No	Artist name (required unless track blob parses)
`person_id`	No	Optional owned contact id from get_people; the track appears on that contact profile and shared history
`year_note`	No	Optional year or remaster note
`request_id`	No	Client idempotency key (retries return original result).
`source_url`	No	Optional https link
`remaster_note`	No	Alias for year_note
`idempotency_key`	No	Alias for request_id.

Output Schema

Name	Required	Description
`track`	Yes	Saved favorite-track record.
`account`	No	The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
`created`	Yes	True when a new favorite was created.
`message`	Yes
`track_id`	Yes
`provenance`	No	Which connector wrote the record and which connected Dayze account received it.
`inspect_url`	No	The Dayze page that shows the saved record.
`inspect_note`	No	What inspect_url opens. Never quote the record id.

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

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 changedOct 2, 2026

addedInput schema / properties / person_id

Added value: +{
+  "description": "Optional owned contact id from get_people; the track appears on that contact profile and shared history",
+  "type": "string"
+}

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": {
+    "created": {
+      "description": "True when a new favorite was created.",
+      "type": "boolean"
+    },
+    "message": {
+      "type": "string"
+    },
+    "track": {
+      "additionalProperties": true,
+      "description": "Saved favorite-track record.",
+      "type": "object"
+    },
+    "track_id": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "track_id",
+    "track",
+    "created",
+    "message"
+  ],
+  "type": "object"
+}

AddedAug 29, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations declare a non-destructive write; the description adds substantial context beyond them — mutation of a specific resource, API key/OAuth scope requirement, that share tokens cannot write, and a $0.10 cost. Auth and cost constraints are exactly the kind of behavior annotations don't 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 MUTATES warning, then usage, example, parameters, and auth constraints in a logical order. Dense but every sentence carries information; the parenthetical cost/API-key note is slightly redundant with the earlier auth sentence.

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?

An output schema exists, so return values need no explanation. For a 10-param write tool, the description covers mutation semantics, auth requirements, cost, idempotency (via schema), and the linking target, leaving nothing an agent needs to call it correctly.

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 100% and already documents the track blob, title/artist, person_id provenance, and aliases, so the description's parameter content largely mirrors structured data. It adds only the synthesized 'track blob or title + artist' alternative, which warrants the baseline 3 rather than a penalty.

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's favorite tracks list at /music. Explicitly distinguishes the target store from music_preferences and chat memory, so an agent can route correctly 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 Guidelines5/5

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

Gives a clear when-to-use trigger ('when they favorite or save a song') plus an explicit when-not ('do not store this as a chat memory or in music_preferences'), and an inline example invocation. Nothing about selection is left 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.