Skip to main content
Glama
Sign In

Dayze — Life Context

by com.dayze
OverviewDiscussionsAdmin

Complete To-do

complete_todo

Mark one to-do done by exact todo_id, only when the user says it is. An elapsed session is not completion. Sessions stay on the calendar and the goal does not change; the reply lists remaining 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": "complete_todo"
  }
}

Input Schema

NameRequiredDescriptionDefault
todo_idYesExact id from get_todos or create_todo. Titles are not accepted.
request_idNoClient idempotency key (retries return original result).
idempotency_keyNoAlias for request_id.

Output Schema

NameRequiredDescriptionDefault
todoNo
accountNoThe Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
changedYes
messageYes
todo_idYes
verifiedYes
provenanceNoWhich connector wrote the record and which connected Dayze account received it.
remaining_sessionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations say non-readOnly, non-destructive, non-openWorld; the description adds genuine value beyond that: sessions remain on the calendar, the goal is unchanged, and the reply enumerates remaining sessions. It also discloses the $0.05 cost and API key requirement, which annotations cannot express. It stops short of stating reversibility via reopen_todo.

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

Conciseness4/5

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

Front-loads the action and identifier, then layers preconditions and side effects compactly. The telegraphic style ('An elapsed session is not completion') is efficient, though the parenthetical cost/auth note is slightly tacked on.

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 the reply format need not be explained, and the description still outlines what the response reports. For a single-required-param mutation with full annotations, the key behavioral facts (state preserved, cost, auth) are all present.

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 the note that titles are not accepted and the idempotency alias semantics. The description repeats 'exact todo_id' but adds no new meaning, so the baseline 3 applies.

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 ('Mark one to-do done') and pins the scope with 'by exact todo_id'. This clearly separates it from update_todo, reopen_todo, schedule_todo, and the session-rescheduling siblings.

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?

Gives an explicit precondition — only when the user says the to-do is done — and adds a strong exclusion: an elapsed session is not completion. It does not name the alternative tool for the session case (reschedule_todo_session/unschedule_todo_session), so routing is slightly incomplete.

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 toolsInspect
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.

Resources