Dayze — Life Context

Update Place Visit

update_place_visit

Correct one stored place visit (visit_id from get_place_visits or log_place_visit): arrived_at, departed_at (null when unknown), arrival_time_precision, or place_id (another of your places, places.id). Fields left out stay. Times read as log_place_visit reads them: YYYY-MM-DD is the day with no clock time; a clock time without an offset is in the account timezone. duration_minutes is recomputed. An edit that would leave two open visits at one place is refused (CONFLICT). Never creates a visit or a place. ($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": {
      "visit_id": "<visit_id>"
    },
    "name": "update_place_visit"
  }
}

Input Schema

Name	Required	Description
`place_id`	No	Move the visit to another of your places (place_id from get_place_visits or get_places).
`visit_id`	Yes	UUID of a place_visits row: visit_id from get_place_visits or log_place_visit.
`arrived_at`	No	ISO 8601 (with offset, or wall time in the account timezone), or YYYY-MM-DD when only the day is known.
`request_id`	No	Client idempotency key (retries return original result).
`departed_at`	No	ISO 8601 or YYYY-MM-DD; null when the departure is unknown.
`idempotency_key`	No	Alias for request_id.
`arrival_time_precision`	No	approximate when the clock time reads a part of day (evening → 19:00).

Output Schema

Name	Required	Description
`visit`	No	The place visit after the change (visit_id, place_id, name, arrived_at, departed_at, duration_minutes, visit_date, arrival_time_specified, arrival_time_approximate).
`account`	No	The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
`changed`	No	Each changed field: { from, to }.
`message`	No
`updated`	No
`timezone`	No	The account timezone visit_date is in.
`provenance`	No	Which connector wrote the record and which connected Dayze account received it.
`arrival_time_note`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 10, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only declare a non-destructive write, but the description adds substantive behavior: partial-update semantics ('Fields left out stay'), the duration_minutes recomputation side effect, a named refusal condition ('two open visits at one place is refused (CONFLICT)'), and the operational constraints ($0.10 cost, API key required). These are exactly the kinds of details annotations cannot convey.

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?

The information is front-loaded (action and editable fields first, edge cases and cost last) and nearly every clause carries operational weight. It is dense to the point of being a run-on, with multiple parentheticals stacked in one paragraph, which slightly hurts scanability.

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?

With an output schema present, return values need no explanation, and the description still covers patch semantics, time parsing, computed fields, the conflict outcome, cost, and auth. There is no material gap an agent would need to guess at before invoking this tool.

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 every parameter is already documented, and the description largely restates the schema's time-format rules (YYYY-MM-DD vs. clock time in account timezone). It adds the meaningful clarification that duration_minutes is recomputed and that departing null means unknown, but the bulk overlaps with structured data, so 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?

Opens with a specific verb and resource ('Correct one stored place visit') and immediately enumerates the editable fields (arrived_at, departed_at, arrival_time_precision, place_id), so the agent knows exactly what can be changed. The 'Never creates a visit or a place' line draws a hard boundary against log_place_visit and create_place.

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?

It names the source of visit_id (get_place_visits or log_place_visit) and states the negative case (no creation), which implicitly routes creation to the sibling log tool. It stops short of explicitly saying when to prefer delete_place_visit over a correction, or how partial edits interact with retrieval, so the routing is clear but not fully exhaustive.

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.