Dayze — Life Context

Add Time Block

add_time_block

Add one time block to a day. The day's other blocks stay. ($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": {
      "date": "<date>",
      "category": "<category>",
      "start_time": "<start_time>",
      "end_time": "<end_time>"
    },
    "name": "add_time_block"
  }
}

Input Schema

Name	Required	Description
`date`	Yes	YYYY-MM-DD.
`note`	No	Note for the block, e.g. Deep work on the draft.
`category`	Yes	Time block category, e.g. focus.
`end_time`	Yes	HH:mm.
`request_id`	No	Client idempotency key (retries return original result).
`start_time`	Yes	HH:mm.
`idempotency_key`	No	Alias for request_id.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 9, 2026
- addedInput schema / properties / category / description
```
Added value: +"Time block category, e.g. focus."
```
- addedInput schema / properties / note / description
```
Added value: +"Note for the block, e.g. Deep work on the draft."
```
AddedNov 5, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, and 'The day's other blocks stay' usefully corroborates the additive, non-destructive semantics. The description also adds genuinely new context the annotations lack — a $0.10 cost and an API key requirement — but says nothing about overlap handling or rate limits.

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 sentences with the core action front-loaded and no filler. The cost and auth note is parenthetical rather than burying the main clause.

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 and annotations cover the safety profile, so the description needn't explain return values; cost and auth are the key extras and they are present. The only real gap is whether overlapping or duplicate blocks are rejected.

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%, including formats for date (YYYY-MM-DD) and times (HH:mm) plus the idempotency alias, so the schema carries the burden and the baseline 3 applies. The description adds no parameter meaning beyond 'one time block to a day'.

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 one time block to a day'), which cleanly separates it from update_time_block and get_time_blocks by implying creation rather than mutation or retrieval. It does not explicitly name a sibling to route against, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not guidance: nothing says whether to use this versus update_time_block for an existing block, or what to do about overlapping blocks. Usage is only implied by the verb 'Add' and the singular 'one time block'.

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.