Dayze — Life Context

Log Place Visit

log_place_visit

MUTATES place_visits for map/history digs (Uber dropoff, address evidence). Required: place (or place_id) + arrived_at/date. arrived_at: a clock time with offset when the user gave a time or part of day (afternoon → 15:00 local); YYYY-MM-DD when only the day is known — the visit is then stored with no clock time and the receipt says "time not specified". arrival_time_precision: approximate when the clock time reads a part of day (evening → 19:00), so readers show "~19:00"; exact (default) only for a time the user gave. Optional: departed_at, source (a provenance tag: uber|mcp|manual|import, not a note), evidence_expense_id (idempotent), city/country/address. Add-only: a repeat on the same day returns the stored visit (duplicate: true, retained, mismatch) and never changes it. Prefer this over stuffing streets only into expenses. ($0.10; API key required)

Input Schema

Name	Required	Description
`city`	No
`date`	No	Alias for arrived_at (YYYY-MM-DD: the day only, time not specified)
`name`	No	Alias for place
`place`	No
`source`	No	Provenance tag (uber, mcp, manual, import, gmail:uber-<id>), not a note.
`address`	No
`country`	No
`place_id`	No
`arrived_at`	No	ISO 8601 with offset (2026-10-21T15:00:00+08:00) when the user gave a time or part of day (morning 09:00, afternoon 15:00, evening 19:00, local); a clock time without an offset is wall time in the account timezone; YYYY-MM-DD when only the day is known (time not specified).
`confidence`	No
`request_id`	No	Client idempotency key (retries return original result).
`departed_at`	No
`idempotency_key`	No	Alias for request_id.
`evidence_event_id`	No
`evidence_expense_id`	No
`arrival_time_precision`	No	approximate when arrived_at reads a part of day the user gave (morning, afternoon, evening → 09:00/15:00/19:00); exact (default) when the user gave the clock time. Ignored for a date-only arrival.

Output Schema

Name	Required	Description
`place`	No	Canonical place record.
`visit`	No	Confirmed same-day outing with visit_date and evidence_refs. A typed place_visits row is primary and carries visit_id (= id); linked event/GPS evidence is reconciled without increasing the count.
`account`	No	The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
`message`	No
`conflict`	No	Add-only write: an open visit to the place from an earlier day was retained (kind: open_visit_retained, visit_id, note); this visit was stored closed at its own arrival.
`mismatch`	No	On a duplicate: how the request differed from the retained visit (field: arrived_at \| departed_at, requested, retained, note); null when it did not.
`place_id`	No
`retained`	No	On a duplicate: the stored visit kept as is (visit_id, visit_date, arrived_at, departed_at, arrival_time_specified, arrival_time_approximate).
`timezone`	No
`duplicate`	No
`provenance`	No	Which connector wrote the record and which connected Dayze account received it.
`inspect_url`	No	The Dayze page that shows the saved record.
`source_note`	No
`inspect_note`	No	What inspect_url opens. Never quote the record id.
`created_place`	No
`arrival_time_note`	No
`arrival_time_specified`	No
`arrival_time_approximate`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 21, 2026

addedInput schema / properties / arrival_time_precision

Added value: +{
+  "description": "approximate when arrived_at reads a part of day the user gave (morning, afternoon, evening → 09:00/15:00/19:00); exact (default) when the user gave the clock time. Ignored for a date-only arrival.",
+  "enum": [
+    "exact",
+    "approximate"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / arrival_time_approximate
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / arrival_time_specified
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / conflict

Added value: +{
+  "additionalProperties": true,
+  "description": "Add-only write: an open visit to the place from an earlier day was retained (kind: open_visit_retained, visit_id, note); this visit was stored closed at its own arrival.",
+  "type": "object"
+}

changedOutput schema / properties / mismatch / description

Previous value: -"On a duplicate: how the request differed from the retained visit (field, requested, retained, note); null when it did not."New value: +"On a duplicate: how the request differed from the retained visit (field: arrived_at | departed_at, requested, retained, note); null when it did not."

changedOutput schema / properties / retained / description

Previous value: -"On a duplicate: the stored visit kept as is (visit_id, visit_date, arrived_at, arrival_time_specified)."New value: +"On a duplicate: the stored visit kept as is (visit_id, visit_date, arrived_at, departed_at, arrival_time_specified, arrival_time_approximate)."

Changed8 schema fields changedOct 21, 2026

changedInput schema / properties / arrived_at / description

Previous value: -"ISO or YYYY-MM-DD"New value: +"ISO 8601 with offset (2026-10-21T15:00:00+08:00) when the user gave a time or part of day (morning 09:00, afternoon 15:00, evening 19:00, local); a clock time without an offset is wall time in the account timezone; YYYY-MM-DD when only the day is known (time not specified)."

changedInput schema / properties / date / description

Previous value: -"Alias for arrived_at"New value: +"Alias for arrived_at (YYYY-MM-DD: the day only, time not specified)"

addedInput schema / properties / source / description

Added value: +"Provenance tag (uber, mcp, manual, import, gmail:uber-<id>), not a note."

addedOutput schema / properties / arrival_time_note

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / mismatch

Added value: +{
+  "additionalProperties": true,
+  "description": "On a duplicate: how the request differed from the retained visit (field, requested, retained, note); null when it did not.",
+  "type": [
+    "object",
+    "null"
+  ]
+}

addedOutput schema / properties / retained

Added value: +{
+  "additionalProperties": true,
+  "description": "On a duplicate: the stored visit kept as is (visit_id, visit_date, arrived_at, arrival_time_specified).",
+  "type": "object"
+}

addedOutput schema / properties / source_note

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / timezone
```
Added value: +{
+  "type": "string"
+}
```

Changed2 schema fields changedOct 21, 2026

addedOutput schema / properties / inspect_note

Added value: +{
+  "description": "What inspect_url opens. Never quote the record id.",
+  "type": "string"
+}

addedOutput schema / properties / inspect_url

Added value: +{
+  "description": "The Dayze page that shows the saved record.",
+  "type": "string"
+}

Changed2 schema fields changedOct 3, 2026

addedOutput schema / properties / account

Added value: +{
+  "additionalProperties": false,
+  "description": "The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.",
+  "properties": {
+    "display_name": {
+      "description": "Account display name.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "handle": {
+      "description": "Account handle, e.g. @goh.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "note": {
+      "description": "How to disclose the account to the user.",
+      "type": "string"
+    },
+    "qa_fixture": {
+      "description": "True for a known QA test account: its records are fixture data, not a real life.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "handle",
+    "display_name",
+    "qa_fixture",
+    "note"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / provenance

Added value: +{
+  "additionalProperties": false,
+  "description": "Which connector wrote the record and which connected Dayze account received it.",
+  "properties": {
+    "account": {
+      "additionalProperties": false,
+      "description": "The Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.",
+      "properties": {
+        "display_name": {
+          "description": "Account display name.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "handle": {
+          "description": "Account handle, e.g. @goh.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "note": {
+          "description": "How to disclose the account to the user.",
+          "type": "string"
+        },
+        "qa_fixture": {
+          "description": "True for a known QA test account: its records are fixture data, not a real life.",
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "handle",
+        "display_name",
+        "qa_fixture",
+        "note"
+      ],
+      "type": "object"
+    },
+    "channel": {
+      "description": "Always mcp_connector.",
+      "type": "string"
+    },
+    "connector": {
+      "additionalProperties": false,
+      "properties": {
+        "kind": {
+          "description": "oauth or api_key.",
+          "type": "string"
+        },
+        "name": {
+          "description": "The connected app or API-key label shown to the account owner.",
+          "type": "string"
+        }
+      },
+      "required": [
+        "kind",
+        "name"
+      ],
+      "type": "object"
+    },
+    "source": {
+      "description": "chatgpt for ChatGPT OAuth writes; mcp for another OAuth app or API key.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "source",
+    "channel",
+    "connector",
+    "account"
+  ],
+  "type": "object"
+}

Changed1 schema field changedOct 3, 2026

changedOutput schema / properties / visit / description

Previous value: -"Normalized place visit. visit_id (= id) is the place_visits row id delete_place_visit takes; null on event/GPS evidence rows."New value: +"Confirmed same-day outing with visit_date and evidence_refs. A typed place_visits row is primary and carries visit_id (= id); linked event/GPS evidence is reconciled without increasing the count."

Changed1 schema field changedSep 28, 2026

changedOutput schema / properties / visit / description

Previous value: -"Normalized place visit."New value: +"Normalized place visit. visit_id (= id) is the place_visits row id delete_place_visit takes; null on event/GPS evidence rows."

AddedSep 13, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations (readOnly=false, destructive=false), it discloses the key behavioral traits: add-only semantics, duplicate handling ('repeat on same day returns stored visit, never changes it'), idempotency, API-key requirement, and cost ($0.10). These are exactly the things an agent cannot infer from structured fields.

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?

Dense but front-loaded: the mutation statement, requirements, and time-format rules come first, followed by optionals and dedupe behavior. The stacked parentheticals make it effortful to parse, but every sentence carries 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?

For a 16-param mutation with an output schema available, the description covers what the agent must decide (required inputs, time semantics, dedupe outcome) and even summarizes the duplicate return shape. Combined with the annotations and output schema, nothing critical is missing.

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?

With only 44% schema coverage across 16 params, the description compensates heavily by explaining arrived_at formats/part-of-day defaults, arrival_time_precision behavior, source as provenance tag not note, and city/country/address. It leaves aliases (name, date), confidence, and evidence_event_id to the schema, keeping it short of a 5.

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+resource ('MUTATES place_visits') and scopes intent to map/history evidence (Uber dropoff, address evidence). It distinguishes itself from neighboring log_* tools by naming the alternative pattern ('Prefer this over stuffing streets only into expenses').

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 clear when-to-use context (map/history digs, rideshare dropoffs, address evidence) and explicitly steers away from stuffing streets into expenses. It lacks an explicit 'when not to use / use log_movement instead' pairing for the most confusable sibling, but the intended usage window is clear.

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

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.