Skip to main content
Glama
Sign In

Dayze — Life Context

by com.dayze
OverviewDiscussionsAdmin

Save Day Note

save_day_note

Add to the user's Day Note for a date (default today, account timezone). mode append (default) adds a line to what is there; replace overwrites the note. ($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": {
      "content": "<content>"
    },
    "name": "save_day_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD. Default today.
modeNoDefault append.
contentYesDay note text, e.g. Quiet day, finished the draft.
request_idNoClient idempotency key (retries return original result).
idempotency_keyNoAlias for request_id.

Output Schema

NameRequiredDescriptionDefault
noteNo
accountNoThe Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
messageNo
provenanceNoWhich connector wrote the record and which connected Dayze account received it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / content / description
      Added value: +"Day note text, e.g. Quiet day, finished the draft."
  2. Added

TDQS

B3.3/5.0
Behavior2/5

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

The description does disclose valuable behavior beyond the annotations: the $0.10 cost, the API-key requirement, the account-timezone default, and the fact that replace destroys existing note content. However, that overwrite behavior conflicts with destructiveHint=false, so an agent that trusts the annotation could destroy content it believed was safe.

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?

Three compact clauses with the core action and scope front-loaded, followed by mode semantics and then cost/auth metadata in parentheses. Nothing is wasted; the only quibble is that pricing/auth could be split out with a clearer label.

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?

An output schema exists, so return values need no explanation, and the description covers the essential call semantics (what is written, where, and under which mode). Missing only a note on retry/idempotency behavior, which the schema already documents.

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 100% and the schema already documents date format/default, mode default, content example, and the request_id/idempotency_key aliasing. The description's mention of append/replace and today/today-timezone adds little that the schema does not already carry, so baseline 3 applies.

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 and resource ('Add to the user's Day Note') plus the scoping dimension (a date, defaulting to today in account timezone). The write verb separates it from the read-only sibling get_day_notes, though no sibling is named explicitly.

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?

Explains the two modes and their defaults ('append (default) adds a line... replace overwrites the note'), which is real when-to-use guidance for mode selection. It gives no guidance on when not to use this tool, or how it relates to siblings like save_day_score or get_day_notes.

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 toolsInspect
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.

Resources