Dayze — Life Context

Update Dream

update_dream

Change a Dream Diary entry by dream_id: title, narrative, dreamed_at, mood, lucidity, people_names, places, tags or notes. Fields left out stay as they are; null clears mood, lucidity or notes. ($0.10; API key required)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dream_id": "<dream_id>"
    },
    "name": "update_dream"
  }
}

Input Schema

Name	Required	Description
`mood`	No	Dream mood such as peaceful, happy, weird, scary or anxious, e.g. peaceful.
`tags`	No	Tags, e.g. ["work"].
`notes`	No	Free-text note, e.g. Follow up next week.
`title`	No	Short dream title, e.g. Flying over the city.
`places`	No	Place names, e.g. ["Grandma's house"].
`dream_id`	Yes	dream_id from get_dreams or log_dream.
`lucidity`	No	How lucid the dream was: none, partial or full, e.g. partial.
`narrative`	No	The dream in the user's own words, e.g. I was flying over the city at night.
`dreamed_at`	No	YYYY-MM-DD or a local date-time.
`request_id`	No	Client idempotency key (retries return original result).
`people_names`	No	Names of people involved, e.g. ["Alex Chen"].
`idempotency_key`	No	Alias for request_id.

Output Schema

Name	Required	Description
`dream`	No	dream_id, dreamed_at, title, mood, lucidity.
`account`	No	The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
`message`	No
`provenance`	No	Which connector wrote the record and which connected Dayze account received it.
`changed_fields`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedNov 9, 2026

addedInput schema / properties / lucidity / description

Added value: +"How lucid the dream was: none, partial or full, e.g. partial."

addedInput schema / properties / mood / description

Added value: +"Dream mood such as peaceful, happy, weird, scary or anxious, e.g. peaceful."

addedInput schema / properties / narrative / description

Added value: +"The dream in the user's own words, e.g. I was flying over the city at night."

addedInput schema / properties / notes / description

Added value: +"Free-text note, e.g. Follow up next week."

addedInput schema / properties / people_names / description

Added value: +"Names of people involved, e.g. [\"Alex Chen\"]."

addedInput schema / properties / people_names / items / description
```
Added value: +"Contact name, e.g. Alex Chen."
```

addedInput schema / properties / places / description

Added value: +"Place names, e.g. [\"Grandma's house\"]."

addedInput schema / properties / places / items / description
```
Added value: +"Place name, e.g. Grandma's house."
```
addedInput schema / properties / tags / description
```
Added value: +"Tags, e.g. [\"work\"]."
```
addedInput schema / properties / tags / items / description
```
Added value: +"Tag, e.g. work."
```

addedInput schema / properties / title / description

Added value: +"Short dream title, e.g. Flying over the city."

AddedNov 4, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations only declare a non-destructive write; the description adds real behavioral context the agent could not otherwise know: omitted fields are preserved (PATCH semantics), null explicitly clears mood/lucidity/notes, and calls cost $0.10 and require an API key. It does not explain how array fields (tags, places, people_names) behave on update or whether changes are reversible, but the partial-update contract is disclosed, consistent with destructiveHint=false.

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?

Two dense, front-loaded sentences plus a terse cost/auth parenthetical — the verb+identifier comes first, then the field list, then the update semantics. The long field enumeration is slightly list-like but every item maps to a real parameter, so nothing is padding.

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?

With an output schema present, return values need not be described, and the definition covers identity, mutability, null semantics, cost and auth for a 12-parameter tool. The remaining gap is array-field update semantics, which matters for a tool with four list-valued parameters.

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 the baseline is 3; the description goes beyond it by adding null-clearing semantics for mood, lucidity and notes and by confirming that unlisted fields are untouched, which the schema's nullable types alone do not convey. It still does not describe array replacement versus merge behavior for tags/places/people_names.

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 and resource ('Change a Dream Diary entry by dream_id') and enumerates exactly which fields are mutable, so the agent can tell this is a partial-update tool for dreams rather than a create or generic update. It is clearly separable from log_dream and from the update_* siblings.

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?

Usage context is clear: dream_id must come from get_dreams or log_dream, which implies this is for existing entries only and that log_dream is the creation path. It does not explicitly say 'do not use this to create' or name alternatives, so it is one step short of full when/when-not guidance.

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.