Dayze — Life Context

Mark Playbook Block

mark_playbook_complete

Check a Playbook block off for a date (default today), by block_title or part of it. completed false unchecks it, and that uncheck can be restored for 30 days. ($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": {
      "block_title": "<block_title>"
    },
    "name": "mark_playbook_complete"
  }
}

Input Schema

Name	Required	Description
`date`	No	YYYY-MM-DD.
`completed`	No	True checks the block off, false unchecks it, e.g. true.
`request_id`	No	Client idempotency key (retries return original result).
`block_title`	Yes	Title or part of a title of the Playbook block, e.g. Morning run.
`idempotency_key`	No	Alias for request_id.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 9, 2026

addedInput schema / properties / block_title / description

Added value: +"Title or part of a title of the Playbook block, e.g. Morning run."

addedInput schema / properties / completed / description

Added value: +"True checks the block off, false unchecks it, e.g. true."

AddedNov 5, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare it is not read-only and not destructive. The description adds real context beyond them: the uncheck reversal window of 30 days, the $0.10 cost, and the API-key requirement. It does not explain idempotency handling or what a repeated call returns, which keeps it short of a 5.

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?

Two sentences, both loaded: the operation and target come first, then the reversal semantics, then cost and auth in a short parenthetical. 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?

An output schema exists, so return values need not be explained, and the description covers the mutation's reversibility, cost, and auth needs. The remaining gap is guidance on when to prefer this over the related complete_todo tool.

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; the description still adds that date defaults to today, which the schema does not state. Its description of the completed toggle echoes the schema rather than extending it, so the gain is modest.

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 concrete verb and resource: check a Playbook block off, with default date behavior and partial-title matching. The agent can tell what the tool acts on, though it never contrasts itself with the sibling complete_todo, so sibling differentiation is absent.

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?

Usage is only implied — you use it to tick off a playbook block. There is no explicit 'use this when...' statement, no exclusions, and no routing toward complete_todo or get_playbook for related tasks.

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.