Dayze — Life Context

Get Dreams

get_dreams

Read-only

The user's Dream Diary, newest first: sleep dreams, not life goals (get_goals). from/to inclusive YYYY-MM-DD in the account timezone; query matches title, narrative, notes and tags; limit (default 50, max 200) with offset, has_more and next_offset. Each row: dream_id, dreamed_on, title, narrative, mood, lucidity, people, places, tags, notes. ($0.05; API key required)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_dreams"
  }
}

Input Schema

Name	Required	Description
`to`	No	Last day, YYYY-MM-DD (account timezone).
`from`	No	First day, YYYY-MM-DD (account timezone).
`limit`	No	Default 50.
`query`	No	Words in the dream.
`offset`	No	next_offset from the last page.

Output Schema

Name	Required	Description	Default
`count`	Yes
`total`	No
`dreams`	No
`has_more`	No
`timezone`	No
`next_offset`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only cover safety (read-only, non-destructive, closed-world); the description adds ordering (newest first), inclusive date semantics with account-timezone interpretation, which fields the query hits, pagination contract (offset / has_more / next_offset), defaults and caps, plus cost ($0.05) and API key requirement. This is substantial context beyond the structured fields.

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 resource and the disambiguation first, then packs range, query, pagination and cost into compact clauses. Dense but readable; the 'Each row: ...' enumeration is the one redundant element since an output schema already exists.

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?

Covers everything an agent needs to call this correctly: scope, ordering, date format and inclusivity, query behavior, paging, limits, and auth/cost. Return shape is additionally handled by the output schema.

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, but the description adds real semantics the schema lacks: from/to are inclusive and interpreted in the account timezone, query matches title, narrative, notes and tags (not just 'words in the dream'), and offset is sourced from next_offset on the previous page.

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?

Names the specific resource ('The user's Dream Diary') and disambiguates it in-line: 'sleep dreams, not life goals (get_goals)'. An agent can distinguish this from get_goals and get_memories without opening a 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?

Clearly frames the tool as a filtered, paginated list of dream entries and points at get_goals as the wrong sibling for life goals. It does not discuss when to prefer get_memories / get_moments or mention prerequisites beyond the API key note, so a small gap remains.

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.