Skip to main content
Glama

Dayze — Life Context

Calendar Events

get_events
Read-only

Authenticated user's calendar events. Prefer explicit from/to (YYYY-MM-DD). Shortcuts: today|week|month|year (calendar year)|decade. Browsing noise excluded by default. Records carry inspect_url (their Dayze page): cite with it, never build a link from an id; a record without one has no page (inspect_note says which). ($0.10; API key required)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNoISO date-time to answer as of (default now), e.g. 2026-09-26T09:00:00+08:00.
toNoInclusive YYYY-MM-DD
fromNoInclusive YYYY-MM-DD (preferred over range)
kindsNoFilter by event_kind: life_event, calendar_block, todo, goal, travel_segment, food_log, health_record, transaction, media_log, work, family, personal. Alias "food" (also meal/drink/snack) matches the displayed Food category: food_log rows plus Meal/Drink/Snack life_events. total/has_more count only matching rows.
limitNoMaximum rows to return, e.g. 20.
queryNoLiteral substring in title, description or location.
rangeNoShortcut window instead of from and to: today, week, month, year, decade or all, e.g. week.
cursorNoOpaque pagination cursor from the previous page's next_cursor, e.g. eyJvIjoyMH0.
offsetNoSkip this many matching rows of a new snapshot (a cursor carries its own).
date_toNoAlias for to.
timezoneNoIANA time zone for today (default: where the user is now, else their home zone).
date_fromNoAlias for from.
redact_piiNotrue: redact contact details, card and account numbers and secrets in description, location and scoreboard, even where this connection may see them. Never unredacts: without travel_secrets:read they are always redacted.
event_kindsNoAlias for kinds.
include_archivedNoInclude archived rows, e.g. false.
include_browsingNoInclude extension "Browsed domain · Xm" auto-events (default false)
include_calendar_blocksNoInclude Focus Time / calendar_block rows (default false)

Output Schema

NameRequiredDescriptionDefault
toYesInclusive YYYY-MM-DD upper bound; null for all records.
capYes
fromYesInclusive YYYY-MM-DD lower bound; null for all records.
rangeYes
totalNo
eventsYes
accountNoThe Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
has_moreNo
orderingNo
timezoneYesResolved timezone used for this event window and as fallback for rows without one.
truncatedYes
expires_atNo
next_cursorNo
server_timeNo
snapshot_atNo
snapshot_idNo
inspect_noteNoHow to cite: link each record with its inspect_url, never a link built from an id; which record types here have no Dayze page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / cursor / description
      Added value: +"Opaque pagination cursor from the previous page's next_cursor, e.g. eyJvIjoyMH0."
    • addedInput schema / properties / event_kinds / items / description
      Added value: +"Event kind, e.g. life_event."
    • addedInput schema / properties / include_archived / description
      Added value: +"Include archived rows, e.g. false."
    • addedInput schema / properties / kinds / items / description
      Added value: +"Event kind, e.g. life_event."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum rows to return, e.g. 20."
    • addedInput schema / properties / range / description
      Added value: +"Shortcut window instead of from and to: today, week, month, year, decade or all, e.g. week."
  2. Changed3 schema fields changed
    • addedInput schema / properties / date_from
      Added value: +{
      +  "description": "Alias for from.",
      +  "type": "string"
      +}
    • addedInput schema / properties / date_to
      Added value: +{
      +  "description": "Alias for to.",
      +  "type": "string"
      +}
    • addedInput schema / properties / query
      Added value: +{
      +  "description": "Literal substring in title, description or location.",
      +  "maxLength": 300,
      +  "type": "string"
      +}
  3. Changed3 schema fields changed
    • addedInput schema / properties / event_kinds
      Added value: +{
      +  "description": "Alias for kinds.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Skip this many matching rows of a new snapshot (a cursor carries its own).",
      +  "type": "number"
      +}
    • addedInput schema / properties / redact_pii
      Added value: +{
      +  "description": "true: redact contact details, card and account numbers and secrets in description, location and scoreboard, even where this connection may see them. Never unredacts: without travel_secrets:read they are always redacted.",
      +  "type": "boolean"
      +}
  4. Changed2 schema fields changed
    • addedInput schema / properties / at
      Added value: +{
      +  "description": "ISO date-time to answer as of (default now), e.g. 2026-09-26T09:00:00+08:00.",
      +  "type": "string"
      +}
    • addedInput schema / properties / timezone
      Added value: +{
      +  "description": "IANA time zone for today (default: where the user is now, else their home zone).",
      +  "type": "string"
      +}
  5. Changed2 schema fields changed
    • 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 / inspect_note
      Added value: +{
      +  "description": "How to cite: link each record with its inspect_url, never a link built from an id; which record types here have no Dayze page.",
      +  "type": "string"
      +}
  6. Changed2 schema fields changed
    • addedOutput schema / properties / timezone
      Added value: +{
      +  "description": "Resolved timezone used for this event window and as fallback for rows without one.",
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "events",
      -  "range",
      -  "from",
      -  "to",
      -  "cap",
      -  "truncated"
      -]New value: +[
      +  "events",
      +  "timezone",
      +  "range",
      +  "from",
      +  "to",
      +  "cap",
      +  "truncated"
      +]
  7. Changed1 schema field changed
    • changedInput schema / properties / kinds / description
      Previous value: -"Filter event_kind e.g. [\"life_event\",\"todo\"]"New value: +"Filter by event_kind: life_event, calendar_block, todo, goal, travel_segment, food_log, health_record, transaction, media_log, work, family, personal. Alias \"food\" (also meal/drink/snack) matches the displayed Food category: food_log rows plus Meal/Drink/Snack life_events. total/has_more count only matching rows."
  8. Changed15 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / include_archived
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / limit
      Added value: +{
      +  "maximum": 500,
      +  "minimum": 1,
      +  "type": "number"
      +}
    • changedInput schema / properties / range / enum
      Previous value: -[
      -  "today",
      -  "week",
      -  "month",
      -  "year",
      -  "decade"
      -]New value: +[
      +  "today",
      +  "week",
      +  "month",
      +  "year",
      +  "decade",
      +  "all"
      +]
    • addedOutput schema / properties / expires_at
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / properties / from / description
      Previous value: -"Inclusive YYYY-MM-DD lower bound."New value: +"Inclusive YYYY-MM-DD lower bound; null for all records."
    • changedOutput schema / properties / from / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • addedOutput schema / properties / has_more
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / next_cursor
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / ordering
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / server_time
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / snapshot_at
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / snapshot_id
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / properties / to / description
      Previous value: -"Inclusive YYYY-MM-DD upper bound."New value: +"Inclusive YYYY-MM-DD upper bound; null for all records."
    • changedOutput schema / properties / to / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
  9. Changed2 schema fields changed
    • addedInput schema / properties / include_calendar_blocks
      Added value: +{
      +  "description": "Include Focus Time / calendar_block rows (default false)",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / kinds
      Added value: +{
      +  "description": "Filter event_kind e.g. [\"life_event\",\"todo\"]",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  10. Changed2 schema fields changed
    • addedInput schema / properties / from
      Added value: +{
      +  "description": "Inclusive YYYY-MM-DD (preferred over range)",
      +  "type": "string"
      +}
    • addedInput schema / properties / to
      Added value: +{
      +  "description": "Inclusive YYYY-MM-DD",
      +  "type": "string"
      +}
  11. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "cap": {
      +      "type": "number"
      +    },
      +    "events": {
      +      "items": {
      +        "additionalProperties": true,
      +        "description": "A Dayze calendar event record.",
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "from": {
      +      "description": "Inclusive YYYY-MM-DD lower bound.",
      +      "type": "string"
      +    },
      +    "range": {
      +      "type": "string"
      +    },
      +    "to": {
      +      "description": "Inclusive YYYY-MM-DD upper bound.",
      +      "type": "string"
      +    },
      +    "total": {
      +      "type": "number"
      +    },
      +    "truncated": {
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "events",
      +    "range",
      +    "from",
      +    "to",
      +    "cap",
      +    "truncated"
      +  ],
      +  "type": "object"
      +}
  12. Changed1 schema field changed
    • addedInput schema / properties / include_browsing
      Added value: +{
      +  "description": "Include extension \"Browsed domain · Xm\" auto-events (default false)",
      +  "type": "boolean"
      +}
  13. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/destructiveHint=false, and the description layers substantial extra context on top: a $0.10 cost, an API-key requirement, the fact that browsing noise is excluded by default, and the citation contract for inspect_url. The rule that a record lacking inspect_url has no page, with inspect_note identifying which, is exactly the kind of behavioral detail annotations cannot express.

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?

Three sentences, each carrying a distinct load: scope, date-window advice, default exclusions, then the inspect_url citation rule. It is telegraphic rather than padded, and the scope statement and cost/auth facts are front-loaded or bracketed where an agent will see them.

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 17-parameter read tool with an output schema and full annotation coverage, the description supplies the non-structural essentials: cost, auth, default exclusions, and the link-construction prohibition. Pagination and filtering mechanics are left to the schema, which is the correct division of labour, so nothing an agent needs in order to call it safely is missing.

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 coverage is 100%, so all 17 parameters, including the enum, aliases and the redact_pii caveat, are already documented in structured fields. The description's added semantics — explicit from/to being preferred and the shortcut vocabulary — largely restate what the schema says ('preferred over range', the range enum). Baseline 3 is appropriate when the schema does the heavy lifting.

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?

Names a concrete resource (the authenticated user's events) scoped to the caller, and adds that records carry an inspect_url pointing at their Dayze page. It stops short of distinguishing the tool from siblings such as get_food_log, get_expenses or get_goals, even though the schema shows it can return food_log, transaction and goal rows — the 'calendar events' framing slightly undersells that breadth.

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?

Gives procedural preference ('Prefer explicit from/to') and enumerates the shortcut windows, which is real guidance on how to call it. It never states when to reach for this tool instead of the specialised siblings, and the exclusion defaults are stated as facts rather than as selection criteria. Usage is therefore implied rather than routed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.