Skip to main content
Glama

Dayze — Life Context

Update Moment (patch a story)

update_moment

Patch one owned moment by moment_id (from log_moment); fields left out are untouched. It stays private. Requires moment_id. Patchable: title, description, moment_date, moment_date_precision, end_date, moment_type, location_name, people, event_id, images, tags. Unknown or other-user moment_id returns an error and creates nothing. person_ids / people_names, media_urls and tags replace the stored list ([] clears); event_id links an owned event (the event is not changed), empty or null unlinks. Visibility is not an argument. Returns changed_fields. Requires API key or OAuth with context.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": {
      "moment_id": "<moment_id>"
    },
    "name": "update_moment"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoAlias for moment_date.
tagsNoReplaces the tags (max 20, 40 characters each). [] clears.
titleNoNew title (max 200). Cannot be empty.
end_dateNoYYYY-MM-DD. Empty or null clears.
event_idNoLink the moment to an owned event (the event is not changed, max 128). Empty or null unlinks.
locationNoAlias for location_name (max 300).
moment_idYesUUID of a moment the user owns (from log_moment, max 128).
media_urlsNoReplaces the image links (max 10). [] clears.
person_idsNoReplaces the tagged people (with people_names, max 25). [] clears. Owned contact ids only.
request_idNoClient idempotency key (retries return original result).
descriptionNoReplaces the story text. Empty or null clears.
moment_dateNoYYYY-MM-DD, YYYY-MM or YYYY (alias date).
moment_timeNoOptional local HH:mm or HH:mm:ss. Empty or null clears (date-only).
moment_typeNoDefault memory.
people_namesNoReplaces the tagged people (with person_ids, max 25, 120 characters each); names match saved contacts only.
location_nameNoReplaces the place (max 300). Empty or null clears. Alias: location.
cover_image_urlNohttps image link (max 2048). Empty or null clears.
idempotency_keyNoAlias for request_id.
moment_date_precisionNoHow exact the date is. YYYY-MM and YYYY default to month and year; circa for "around then".

Output Schema

NameRequiredDescriptionDefault
momentYesA moment: a story or memory, private to the owner. event_id links the event it is about.
accountNoThe Dayze account this data belongs to. With more than one Dayze connection, name it in the answer.
messageYes
provenanceNoWhich connector wrote the record and which connected Dayze account received it.
invalidatesNo
people_taggedYes
changed_fieldsYesThe columns this call changed; empty when nothing differed.
unresolved_peopleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / media_urls / items / description
      Added value: +"HTTPS image URL, e.g. https://example.com/photo.jpg."
    • addedInput schema / properties / people_names / items / description
      Added value: +"Contact name, e.g. Alex Chen."
    • addedInput schema / properties / person_ids / items / description
      Added value: +"Contact id, e.g. 3f2a1b4c-8d9e-6f01-c2b3-c4d5e6f70809."
    • addedInput schema / properties / tags / items / description
      Added value: +"Tag, e.g. work."
  2. Changed23 schema fields changed
    • changedInput schema / properties / cover_image_url / description
      Previous value: -"https image link. Empty or null clears."New value: +"https image link (max 2048). Empty or null clears."
    • addedInput schema / properties / cover_image_url / maxLength
      Added value: +2048
    • changedInput schema / properties / event_id / description
      Previous value: -"Link the moment to an owned event (the event is not changed). Empty or null unlinks."New value: +"Link the moment to an owned event (the event is not changed, max 128). Empty or null unlinks."
    • addedInput schema / properties / event_id / maxLength
      Added value: +128
    • changedInput schema / properties / location / description
      Previous value: -"Alias for location_name."New value: +"Alias for location_name (max 300)."
    • addedInput schema / properties / location / maxLength
      Added value: +300
    • changedInput schema / properties / location_name / description
      Previous value: -"Replaces the place. Empty or null clears. Alias: location."New value: +"Replaces the place (max 300). Empty or null clears. Alias: location."
    • addedInput schema / properties / location_name / maxLength
      Added value: +300
    • changedInput schema / properties / media_urls / description
      Previous value: -"Replaces the image links. [] clears."New value: +"Replaces the image links (max 10). [] clears."
    • addedInput schema / properties / media_urls / items / maxLength
      Added value: +2048
    • addedInput schema / properties / media_urls / maxItems
      Added value: +10
    • changedInput schema / properties / moment_id / description
      Previous value: -"UUID of a moment the user owns (from log_moment)."New value: +"UUID of a moment the user owns (from log_moment, max 128)."
    • addedInput schema / properties / moment_id / maxLength
      Added value: +128
    • changedInput schema / properties / people_names / description
      Previous value: -"Replaces the tagged people (with person_ids); names match saved contacts only."New value: +"Replaces the tagged people (with person_ids, max 25, 120 characters each); names match saved contacts only."
    • addedInput schema / properties / people_names / items / maxLength
      Added value: +120
    • addedInput schema / properties / people_names / maxItems
      Added value: +25
    • changedInput schema / properties / person_ids / description
      Previous value: -"Replaces the tagged people (with people_names). [] clears. Owned contact ids only."New value: +"Replaces the tagged people (with people_names, max 25). [] clears. Owned contact ids only."
    • addedInput schema / properties / person_ids / items / maxLength
      Added value: +64
    • addedInput schema / properties / person_ids / maxItems
      Added value: +25
    • changedInput schema / properties / tags / description
      Previous value: -"Replaces the tags. [] clears."New value: +"Replaces the tags (max 20, 40 characters each). [] clears."
    • addedInput schema / properties / tags / items / maxLength
      Added value: +40
    • addedInput schema / properties / tags / maxItems
      Added value: +20
    • addedInput schema / properties / title / maxLength
      Added value: +200
  3. Changed10 schema fields changed
    • addedOutput schema / properties / moment / properties / ai_summary
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / moment / properties / is_featured
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / moment / properties / is_pinned
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / moment / properties / is_recurring
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / moment / properties / location_lat
      Added value: +{
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / moment / properties / location_lng
      Added value: +{
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / moment / properties / location_place_id
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / moment / properties / merged_provenance
      Added value: +{
      +  "items": {
      +    "additionalProperties": true,
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / moment / properties / recurrence_rule
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / moment / properties / sentiment
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  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. Changed1 schema field changed
    • addedInput schema / properties / moment_time
      Added value: +{
      +  "description": "Optional local HH:mm or HH:mm:ss. Empty or null clears (date-only).",
      +  "type": "string"
      +}
  6. Added

TDQS

A4.4/5.0
Behavior5/5

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

With annotations only declaring non-destructive/non-read-only, the description carries real behavioral weight: list fields replace wholesale and [] clears, event_id links an owned event and empty/null unlinks, unknown or other-user ids error out and create nothing, and auth requires API key or OAuth with context.write at a stated $0.10 cost. It also names the return field (changed_fields) and the privacy invariant, which the annotations do not 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?

Front-loaded with identity and patch semantics, then field list, then edge behavior and auth — a sensible order with little filler. Minor redundancy remains: moment_id is stated three times (source, 'Requires moment_id', and required schema) and API-key requirement appears twice in the final parenthetical.

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 19-parameter mutation with an output schema, everything an agent needs to call it correctly is present: partial-update contract, replace/clear rules, ownership failure mode, auth scope, cost, and what is returned. The output schema covers return detail, so no further explanation is required.

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 the baseline is 3, and most of the description's parameter talk (replace/clear semantics, event linking) is already stated per-property in the schema. The one addition is the consolidated list of patchable fields, but it uses loose names ('images', 'people') that do not match the actual properties (media_urls, cover_image_url, person_ids, people_names), which adds slight ambiguity rather than clarity.

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 and resource ('Patch one owned moment by moment_id') and immediately scopes it against the sibling that produces the id ('from log_moment'). The partial-update clause ('fields left out are untouched') makes the semantics distinguishable from delete_moment or a full-replace update.

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 context for when this applies: you need an owned moment_id from log_moment, and omitted fields stay untouched. It also states what the tool will NOT do (visibility is not an argument, the linked event is not changed), but it never names an alternative for callers who want a full replace or a create.

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.