list_day_notes
Lists the user’s day notes for a date range of up to 92 days. A day note is the user’s one note about a whole calendar date (for example “Travel day” or “Sick”). It is not an Occurrence note, has no status, and never changes Completed, Not Completed, Unresolved, Needs decision, adherence, or reminders. Use it for questions about how a day went overall. Only dates with a saved note are returned.
Permission and annotations
Required scope: cadence.read. Contract 1.7.0; available since 1.1.0.
title: “List day notes”readOnlyHint: truedestructiveHint: falseidempotentHint: trueopenWorldHint: false
Reads account data and changes nothing, so readOnlyHint is true. Claude runs read-only tools without per-call confirmation, and OpenAI asks for readOnlyHint on every read. openWorldHint is false because the tool reaches only the user’s own Cadence account.
Input
Required means required within the containing object. Variant fields apply only to that variant; children of nullable values apply when non-null. Unknown fields are rejected.
| Field | Required | Type | Meaning and constraints |
|---|---|---|---|
start_local_date |
yes | string | First local date, inclusive.; format: date |
end_local_date |
yes | string | Last local date, inclusive.; format: date |
Output
Required means required within the containing object. Variant fields apply only to that variant; children of nullable values apply when non-null. Unknown fields are rejected.
| Field | Required | Type | Meaning and constraints |
|---|---|---|---|
timezone |
yes | string | IANA timezone name.; minLength: 1; maxLength: 64; pattern: ^[A-Za-z0-9_+\-/]+$ |
day_notes |
yes | array | maxItems: 92 |
day_notes[] |
yes | object | |
day_notes[].id |
yes | string | format: uuid |
day_notes[].local_date |
yes | string | Calendar date (YYYY-MM-DD) in the account timezone.; format: date |
day_notes[].note |
yes | string or null | Day note text. Null after the user cleared it. |
day_notes[].revision |
yes | string | Opaque version token of this record. Send it back as expected_revision to avoid overwriting a newer change.; minLength: 1; maxLength: 128; pattern: ^[A-Za-z0-9._:-]+$ |
day_notes[].updated_at |
yes | string | format: date-time; pattern: [Zz]$ |
Example call
Synthetic contract fixture. Replace identifiers and dates with records returned for your account. This is the SDK tools/call payload, not a complete HTTP request.
{
"name": "list_day_notes",
"arguments": {
"start_local_date": "2026-03-01",
"end_local_date": "2026-03-31"
}
}
Example result
Synthetic success data from a contract fixture, shown as structuredContent. Input and output examples validate independently; they are not a recorded transaction.
{
"timezone": "America/New_York",
"day_notes": [
{
"id": "00000006-1111-4111-8111-000000000006",
"local_date": "2026-03-08",
"note": "Travel day",
"revision": "2026-03-08T07:30:00Z",
"updated_at": "2026-03-08T07:30:00Z"
}
]
}
Errors
invalid_input: The input does not match the tool’s schema or rules.field_errorsnames each problem.authentication_required: The access token is missing, expired, revoked, or issued for another resource. Reconnect Cadence.rate_limited: Too many requests for this connection. Retry afterretry_after_seconds.service_unavailable: Cadence integrations are temporarily unavailable.internal_error: Cadence could not complete the request. Nothing is assumed to have changed; retry once with the sameidempotency_key.limit_exceeded: The request asks for more than a contract limit allows, such as too long a date range or too large a result. Narrow the request.
Output size limits can also return limit_exceeded. See error handling, limits, and safe retries.