Dayze — Life Context

Unschedule To-do Session

unschedule_todo_session

Take one session off the calendar by exact session_id. The to-do, its due date and its completion stay. Restorable from the archived event. ($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>"
    },
    "name": "unschedule_todo_session"
  }
}

Input Schema

Name	Required	Description
`request_id`	No	Client idempotency key (retries return original result).
`session_id`	Yes	Exact session id from get_todos or schedule_todo.
`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.
`changed`	Yes
`message`	Yes
`todo_id`	Yes
`event_id`	No
`verified`	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.

AddedNov 7, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the description adds genuinely new context beyond that: the operation is reversible because the event is archived, and only the calendar session is affected while the to-do record persists. It also surfaces the $0.05 cost and API-key requirement, which annotations do not cover; only missing piece is any rate-limit or failure behavior.

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 short declarative sentences: action and identifier first, then what is preserved, then reversibility, with cost/auth kept in a trailing parenthetical. No sentence is redundant and nothing buries the critical scoping information.

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?

An output schema exists so return values need not be described, and the description covers the mutation's blast radius, reversibility, auth requirement and price. For a single-required-parameter unschedule operation, nothing an agent needs in order to call it correctly is absent.

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 description coverage is 100%, so request_id/idempotency_key aliasing and the session_id source are already documented. The description reinforces that the id must be an exact match, but adds no format or lookup mechanics beyond the schema, so the 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?

Uses a specific verb phrase ("Take one session off the calendar") against a named resource with an explicit scope (one session, exact session_id), which an agent can distinguish from schedule_todo or reschedule_todo_session without opening the schema. It stops short of naming those siblings, so differentiation is inferred from the verb rather than stated.

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?

The description clarifies the effect boundary (to-do, due date, completion stay) which implicitly tells the agent this is not a to-do deletion, but it never states when to prefer this over reschedule_todo_session or how it relates to schedule_todo. Usage is implied rather than directed.

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.