Dayze — Life Context

Reschedule To-do Session

reschedule_todo_session

Move one session by exact session_id: the same event moves, and the due date does not. Give the full new timing, as for schedule_todo. ($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": {
      "session_id": "<session_id>",
      "date": "<date>"
    },
    "name": "reschedule_todo_session"
  }
}

Input Schema

Name	Required	Description
`date`	Yes	The day of the session. Ask the user; never assume today.
`all_day`	No	True only when the user chose a whole day. Takes no times.
`end_date`	No	End date YYYY-MM-DD, e.g. 2026-10-18.
`end_time`	No	HH:MM in the given time zone.
`timezone`	No	IANA time zone, e.g. Asia/Singapore.
`request_id`	No	Client idempotency key (retries return original result).
`session_id`	Yes	Exact session id from get_todos or schedule_todo.
`start_time`	No	HH:MM in the given time zone.
`idempotency_key`	No	Alias for request_id.
`duration_minutes`	No	Session length in minutes, e.g. 45.
`expected_updated_at`	No	The updated_at you last read, for conflict detection, e.g. 2026-10-17T15:30:00Z.

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.
`goal_id`	No
`message`	Yes
`todo_id`	Yes
`event_id`	Yes
`todo_url`	No
`verified`	Yes
`event_url`	No
`allocation`	Yes
`provenance`	No	Which connector wrote the record and which connected Dayze account received it.
`session_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 9, 2026
- addedInput schema / properties / duration_minutes / description
```
Added value: +"Session length in minutes, e.g. 45."
```
- addedInput schema / properties / end_date / description
```
Added value: +"End date YYYY-MM-DD, e.g. 2026-10-18."
```
- addedInput schema / properties / expected_updated_at / description
```
Added value: +"The updated_at you last read, for conflict detection, e.g. 2026-10-17T15:30:00Z."
```
AddedNov 7, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare a non-read-only, non-destructive, closed-world mutation, so the safety bar is partly met. The description adds real context beyond them: a per-call cost ($0.05), an API-key requirement, and the important semantic that only the event moves, not the due date.

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?

Three compact clauses, front-loaded with the core action and its key side-effect, followed by the timing requirement and cost/auth note. No filler and nothing buried.

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 an 11-parameter mutation with an output schema and annotations, the description covers purpose, timing input expectation, cost, and auth. It leaves idempotency and conflict detection (request_id, expected_updated_at) entirely to the schema, which is acceptable given the high coverage but is a small missed opportunity.

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 parameter documentation is already strong. The description nonetheless adds meaning the schema cannot: the session must be addressed by exact session_id, and the caller must supply the complete new timing rather than a partial patch, with schedule_todo as the reference.

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 ('Move one session by exact session_id') and immediately pins down a non-obvious invariant: the same event moves while the due date does not. That differentiates it from schedule_todo and unschedule_todo_session without needing either schema.

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?

Implies the context of use (an existing session identified by session_id) and defers to schedule_todo for how to supply the full new timing. It never explicitly says when to pick this over re-scheduling via schedule_todo or unschedule_todo_session, and gives no exclusions.

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.