Skip to main content
Glama

Dayze — Life Context

Update Event (calendar patch)

update_event

MUTATES one existing calendar event the authenticated user owns. Required: event_id (UUID). Optional patch (same fields as log_event): title, date / event_date, time / event_time, end_date, end_time, location, description (alias notes), category, external_url, image_url, timezone, visibility, people / with / person_ids, scoreboard (merged; null clears), reminder_enabled (false turns the push reminder off; needs a timed event to turn on), reminder_minutes_before. Adds a bedtime to a wake-only sleep: event_time (and event_date / end_date when it was the night before). Unknown or other-user event_id returns an error and does not create a row. For food-diary meals, prefer update_food (it syncs the mirrored event). Rebuilds life_state. Requires API key or OAuth with scope context. Share tokens cannot write. ($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": {
      "event_id": "<event_id>"
    },
    "name": "update_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoAlias for event_date
timeNoAlias for event_time
withNoAlias: people
notesNoAlias for description
titleNoUpdated title (replaces). Cannot be empty.
peopleNoPeople names or person UUIDs to add (event_people role=with). Does not remove existing tags.
categoryNoCategory, e.g. sleep, work
end_dateNoOptional end date YYYY-MM-DD (multi-day, or a night that ends the next day)
end_timeNoOptional end time (same formats as event_time)
event_idYesUUID of a calendar event the authenticated user owns
locationNoEmpty or null clears
timezoneNoIANA timezone for wall-clock display. Empty or null clears.
image_urlNoCover image URL. Empty or null clears.
event_dateNoStart date YYYY-MM-DD, YYYY-MM, or YYYY. Alias: date.
event_timeNoStart time: 8pm, 20:00, or 20:00:00. Empty or null clears. Alias: time.
person_idsNoOwned person ids
request_idNoClient idempotency key (retries return original successful result)
scoreboardNoStatus data; state required if new; null clears
visibilityNoUpdates both events.visibility and the enforced events.is_private flag
descriptionNoNotes about the event (replaces). Empty or null clears. Alias: notes.
person_nameNoPerson to tag
external_urlNoLink to the source page, e.g. https://example.com/events/42.
people_namesNoAlias: people
date_precisionNoSoft date precision stored in metadata
idempotency_keyNoAlias for request_id
reminder_enabledNoTurn the push reminder on or off. A timed event is needed to turn it on; all-day events stay off.
expected_updated_atNoOptional ISO updated_at you last read. Write applies only if unchanged; otherwise code "conflict" with the current record and changes nothing.
reminder_minutes_beforeNoPush lead time in minutes (snapped to 0, 5, 15, 30, 60, 1440 or 10080)

Output Schema

NameRequiredDescriptionDefault
eventYesA Dayze calendar event record.
accountNoThe Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
changedYesChanged fields with before and after values.
provenanceNoWhich connector wrote the record and which connected Dayze account received it.
people_taggedYes
unresolved_peopleYes
life_state_rebuiltYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed30 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"e.g. sleep, funeral, family, work, travel. Stored as events.category and event_type."New value: +"Category, e.g. sleep, work"
    • changedInput schema / properties / date / description
      Previous value: -"Alias for event_date."New value: +"Alias for event_date"
    • changedInput schema / properties / date_precision / description
      Previous value: -"Soft date precision stored in metadata."New value: +"Soft date precision stored in metadata"
    • changedInput schema / properties / end_date / description
      Previous value: -"Optional end date YYYY-MM-DD (multi-day, or a night that ends the next day)."New value: +"Optional end date YYYY-MM-DD (multi-day, or a night that ends the next day)"
    • changedInput schema / properties / end_time / description
      Previous value: -"Optional end time (same formats as event_time)."New value: +"Optional end time (same formats as event_time)"
    • changedInput schema / properties / expected_updated_at / description
      Previous value: -"Optional. The updated_at you last read for this record (ISO timestamp). The write applies only if the record has not changed since; otherwise it returns code \"conflict\" with the current record and changes nothing."New value: +"Optional ISO updated_at you last read. Write applies only if unchanged; otherwise code \"conflict\" with the current record and changes nothing."
    • addedInput schema / properties / external_url / description
      Added value: +"Link to the source page, e.g. https://example.com/events/42."
    • changedInput schema / properties / idempotency_key / description
      Previous value: -"Alias for request_id."New value: +"Alias for request_id"
    • changedInput schema / properties / notes / description
      Previous value: -"Alias for description."New value: +"Alias for description"
    • addedInput schema / properties / people / items / description
      Added value: +"Contact name or id, e.g. Alex."
    • changedInput schema / properties / people_names / description
      Previous value: -"Alias for people."New value: +"Alias: people"
    • addedInput schema / properties / people_names / items / description
      Added value: +"Name"
    • changedInput schema / properties / person_ids / description
      Previous value: -"Owned person UUIDs to tag (user-scoped)."New value: +"Owned person ids"
    • addedInput schema / properties / person_ids / items / description
      Added value: +"Id"
    • changedInput schema / properties / person_name / description
      Previous value: -"One person to tag, by name."New value: +"Person to tag"
    • changedInput schema / properties / reminder_minutes_before / description
      Previous value: -"Push lead time in minutes (snapped to 0, 5, 15, 30, 60, 1440 or 10080)."New value: +"Push lead time in minutes (snapped to 0, 5, 15, 30, 60, 1440 or 10080)"
    • changedInput schema / properties / request_id / description
      Previous value: -"Client idempotency key (retries return original successful result)."New value: +"Client idempotency key (retries return original successful result)"
    • changedInput schema / properties / scoreboard / description
      Previous value: -"Operating status as data (not description prose). state is required when the event has no scoreboard yet. On update_event fields merge; a null field clears it; scoreboard null removes the record."New value: +"Status data; state required if new; null clears"
    • addedInput schema / properties / scoreboard / properties / blocker / description
      Added value: +"What blocks it"
    • addedInput schema / properties / scoreboard / properties / evidence / description
      Added value: +"Evidence note"
    • changedInput schema / properties / scoreboard / properties / last_verified / description
      Previous value: -"YYYY-MM-DD"New value: +"Last check YYYY-MM-DD"
    • changedInput schema / properties / scoreboard / properties / metric / description
      Previous value: -"Progress readout, e.g. 2/5"New value: +"Progress, e.g. 2/5"
    • changedInput schema / properties / scoreboard / properties / next_review / description
      Previous value: -"YYYY-MM-DD"New value: +"Next review YYYY-MM-DD"
    • addedInput schema / properties / scoreboard / properties / next_step / description
      Added value: +"Next action"
    • addedInput schema / properties / scoreboard / properties / owner / description
      Added value: +"Owner name"
    • addedInput schema / properties / scoreboard / properties / state / description
      Added value: +"Operating state"
    • changedInput schema / properties / time / description
      Previous value: -"Alias for event_time."New value: +"Alias for event_time"
    • changedInput schema / properties / visibility / description
      Previous value: -"Updates both events.visibility and the enforced events.is_private flag."New value: +"Updates both events.visibility and the enforced events.is_private flag"
    • changedInput schema / properties / with / description
      Previous value: -"Alias for people."New value: +"Alias: people"
    • addedInput schema / properties / with / items / description
      Added value: +"Name"
  2. Changed1 schema field changed
    • addedInput schema / properties / expected_updated_at
      Added value: +{
      +  "description": "Optional. The updated_at you last read for this record (ISO timestamp). The write applies only if the record has not changed since; otherwise it returns code \"conflict\" with the current record and changes nothing.",
      +  "type": "string"
      +}
  3. Changed2 schema fields changed
    • addedInput schema / properties / reminder_enabled
      Added value: +{
      +  "description": "Turn the push reminder on or off. A timed event is needed to turn it on; all-day events stay off.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / reminder_minutes_before
      Added value: +{
      +  "description": "Push lead time in minutes (snapped to 0, 5, 15, 30, 60, 1440 or 10080).",
      +  "type": "number"
      +}
  4. 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 / 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"
      +}
  5. Changed8 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"e.g. funeral, family, work, travel. Stored as events.category and event_type."New value: +"e.g. sleep, funeral, family, work, travel. Stored as events.category and event_type."
    • changedInput schema / properties / description / description
      Previous value: -"Empty or null clears"New value: +"Notes about the event (replaces). Empty or null clears. Alias: notes."
    • changedInput schema / properties / end_date / description
      Previous value: -"Optional end date YYYY-MM-DD (all-day multi-day)."New value: +"Optional end date YYYY-MM-DD (multi-day, or a night that ends the next day)."
    • addedInput schema / properties / image_url
      Added value: +{
      +  "description": "Cover image URL. Empty or null clears.",
      +  "type": "string"
      +}
    • addedInput schema / properties / notes
      Added value: +{
      +  "description": "Alias for description.",
      +  "type": "string"
      +}
    • addedInput schema / properties / people_names / description
      Added value: +"Alias for people."
    • addedInput schema / properties / person_name / description
      Added value: +"One person to tag, by name."
    • addedInput schema / properties / timezone
      Added value: +{
      +  "description": "IANA timezone for wall-clock display. Empty or null clears.",
      +  "type": "string"
      +}
  6. Changed1 schema field changed
    • addedInput schema / properties / scoreboard
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Operating status as data (not description prose). state is required when the event has no scoreboard yet. On update_event fields merge; a null field clears it; scoreboard null removes the record.",
      +  "properties": {
      +    "blocker": {
      +      "type": "string"
      +    },
      +    "evidence": {
      +      "type": "string"
      +    },
      +    "last_verified": {
      +      "description": "YYYY-MM-DD",
      +      "type": "string"
      +    },
      +    "metric": {
      +      "description": "Progress readout, e.g. 2/5",
      +      "type": "string"
      +    },
      +    "next_review": {
      +      "description": "YYYY-MM-DD",
      +      "type": "string"
      +    },
      +    "next_step": {
      +      "type": "string"
      +    },
      +    "owner": {
      +      "type": "string"
      +    },
      +    "state": {
      +      "enum": [
      +        "not_started",
      +        "on_track",
      +        "at_risk",
      +        "blocked",
      +        "done"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  7. Changed1 schema field changed
    • addedInput schema / properties / visibility
      Added value: +{
      +  "description": "Updates both events.visibility and the enforced events.is_private flag.",
      +  "enum": [
      +    "private",
      +    "friends",
      +    "public"
      +  ],
      +  "type": "string"
      +}
  8. Changed1 schema field changed
    • changedInput schema / properties / request_id / description
      Previous value: -"Client idempotency key (retries return original result)."New value: +"Client idempotency key (retries return original successful result)."
  9. Changed2 schema fields changed
    • addedInput schema / properties / date_precision
      Added value: +{
      +  "description": "Soft date precision stored in metadata.",
      +  "enum": [
      +    "day",
      +    "month",
      +    "year",
      +    "approx"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / event_date / description
      Previous value: -"Start date YYYY-MM-DD. Alias: date."New value: +"Start date YYYY-MM-DD, YYYY-MM, or YYYY. Alias: date."
  10. Changed2 schema fields changed
    • addedInput schema / properties / idempotency_key
      Added value: +{
      +  "description": "Alias for request_id.",
      +  "type": "string"
      +}
    • addedInput schema / properties / request_id
      Added value: +{
      +  "description": "Client idempotency key (retries return original result).",
      +  "type": "string"
      +}
  11. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "changed": {
      +      "additionalProperties": true,
      +      "description": "Changed fields with before and after values.",
      +      "type": "object"
      +    },
      +    "event": {
      +      "additionalProperties": true,
      +      "description": "A Dayze calendar event record.",
      +      "type": "object"
      +    },
      +    "life_state_rebuilt": {
      +      "type": "boolean"
      +    },
      +    "people_tagged": {
      +      "items": {
      +        "additionalProperties": true,
      +        "description": "A Dayze person or contact record.",
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "unresolved_people": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "event",
      +    "changed",
      +    "people_tagged",
      +    "unresolved_people",
      +    "life_state_rebuilt"
      +  ],
      +  "type": "object"
      +}
  12. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations only declare readOnly=false, destructiveHint=false, openWorld=false; the description adds real value on top: API key or OAuth scope required, share tokens cannot write, $0.10 cost, unknown or other-user event_id errors out without creating a row, and the call rebuilds life_state. It does not flag that null/empty values clear existing fields (a surprisingly destructive side effect of a patch), which is the main omission given destructiveHint=false.

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-loaded with the constraint and requirement before the long field inventory, and every clause carries information an agent needs (auth, cost, error behavior, alternative). The parenthetical list of patch fields largely restates the schema and could be compressed, which keeps it from a 5.

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 28-parameter tool with a nested object and an output schema, the description covers the things structured fields cannot: authorization modes, cost, idempotency/conflict hints, error semantics on foreign IDs, systemic side effects, and the preferred sibling. 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% so baseline is 3, but the description still adds cross-field meaning the schema cannot: the alias clusters (date/event_date, time/event_time, people/with/person_ids), that scoreboard is merged while null clears, and that reminder_enabled can only be turned on for timed events. Only the bedtime-creation case adds truly new semantics beyond the schema, so it stops short of 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?

Opens with a specific verb (MUTATES), the exact resource (one existing calendar event), and the ownership scope (the authenticated user owns). It even tells the agent how it differs from log_event (same patch fields) and from update_food, so it is distinguishable without opening any schema.

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?

Explicitly routes food-diary meals to update_food because that tool syncs the mirrored event, and gives a concrete conditional recipe for adding a bedtime to a wake-only sleep. It does not address when to prefer archive_event, delete_event, or apply_event_fact_correction, but the mutation-only framing makes the delete distinction reasonably clear.

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.