Dayze — Life Context

Update To-do

update_todo

Patch one to-do by exact todo_id. Omitted fields stay as they are; null clears due_date, due_time, description or goal_id. goal_id links it to a goal, null detaches it. Does not move calendar sessions. ($0.05; 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": {
      "todo_id": "<todo_id>"
    },
    "name": "update_todo"
  }
}

Input Schema

Name	Required	Description
`title`	No	To-do title, e.g. Renew passport.
`goal_id`	No	Goal id, e.g. 3f2a1b4c-8d9e-6f01-c2b3-c4d5e6f70809.
`todo_id`	Yes	Exact id from get_todos or create_todo. Titles are not accepted.
`due_date`	No	Due date YYYY-MM-DD; null clears, e.g. 2026-10-31.
`due_time`	No	HH:MM in the given time zone.
`priority`	No	Priority level: high, medium or low, e.g. medium.
`request_id`	No	Client idempotency key (retries return original result).
`description`	No	To-do details; null clears, e.g. Bring the signed form.
`due_timezone`	No	IANA time zone, e.g. Asia/Singapore.
`idempotency_key`	No	Alias for request_id.

Output Schema

Name	Required	Description
`todo`	No
`account`	No	The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
`message`	Yes
`todo_id`	Yes
`verified`	Yes
`provenance`	No	Which connector wrote the record and which connected Dayze account received it.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 9, 2026

addedInput schema / properties / description / description

Added value: +"To-do details; null clears, e.g. Bring the signed form."

addedInput schema / properties / due_date / description

Added value: +"Due date YYYY-MM-DD; null clears, e.g. 2026-10-31."

addedInput schema / properties / goal_id / description

Added value: +"Goal id, e.g. 3f2a1b4c-8d9e-6f01-c2b3-c4d5e6f70809."

addedInput schema / properties / priority / description

Added value: +"Priority level: high, medium or low, e.g. medium."

addedInput schema / properties / title / description

Added value: +"To-do title, e.g. Renew passport."

AddedNov 7, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Beyond the annotations (which only say non-read-only, non-destructive, closed-world), it discloses the crucial omitted-vs-null distinction, that null detaches goal_id, that calendar sessions are untouched, and the cost/auth requirements. Those are exactly the behavioral facts an agent needs before calling a mutating tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short clauses, front-loaded with the operation and identifier, then the patch/null rule, then the side-effect boundary, then cost and auth. No sentence is redundant or padded.

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 10-parameter mutation with an output schema and full schema coverage, the description covers the risky semantics (null clearing, goal linking, no calendar side effects) and operating constraints. The only omission is idempotency/retry behavior, which the schema documents but the description does not reinforce.

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, but the description adds cross-parameter meaning the schema only states field-by-field: omitted fields are left unchanged while null clears due_date, due_time, description, or goal_id. It does not explain request_id/idempotency_key or due_timezone interactions, which the schema carries alone.

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?

"Patch one to-do by exact todo_id" names a specific verb and resource and pins the identifier semantics (exact id, not title). It implicitly separates itself from create_todo/complete_todo by being a partial-update operation, but it never names a sibling to route against.

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?

The description establishes clear usage context: partial update, omitted fields preserved, and an explicit boundary ("Does not move calendar sessions"), which steers an agent away from reschedule_todo_session. It stops short of saying which sibling to use for completing, reopening, or rescheduling a to-do.

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.