Skip to main content
Glama

Dayze — Life Context

Update Contact (CRM write)

update_person

MUTATES one owned Dayze contact by person_id. context_tags-only patches ok (full desired array; repeats are no-ops). last_interaction_at corrects last touch (owner-set). personal-write OAuth needs request_id (unique per write; reuse to retry). Omitted fields stay. undo_contact_change(change_id) reverts. Requires context.write; 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": {
      "person_id": "<person_id>"
    },
    "name": "update_person"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoRename contact (also refreshes URL slug). Prefer over create+merge for spelling fixes
tierNoRelationship priority. VIP stays in inner_circle even when not favorited
emailNoemail. Omit to leave unchanged; null or blank clears.
notesNoReplaces people.notes (does not append). Empty or null clears
phoneNophone. Omit to leave unchanged; null or blank clears.
genderNoNull or blank clears
addressNoPostal address (one line). Null or blank clears
companyNocompany. Omit to leave unchanged; null or blank clears.
walletsNoENS (.eth) / SNS (.sol) names and/or addresses for this contact. Merged into social_handles (legacy ens/ens_address kept); empty array clears wallet keys only.
birthdayNoYYYY, YYYY-MM, YYYY-MM-DD, or MM-DD / --MM-DD (year unknown; 02-29 ok). Null/empty clears
pronounsNoe.g. she/her. Null or blank clears
first_metNoWhen/how they first met (free text). Null or blank clears
person_idYesUUID of a person the authenticated user owns
birth_timeNoHH:MM 24-hour. Null clears
death_dateNoYYYY-MM-DD; marks the contact deceased. Null clears
occupationNoOccupation / job title. Omit to leave unchanged; null or blank clears.
request_idNoRequired on personal-write OAuth. Unique for a new write; reuse for an exact retry.
is_deceasedNofalse also clears death_date and the memorial reminder
is_favoriteNoFavorite flag. Favorites (and VIP) appear in get_context_pack inner_circle
cadence_daysNoCheck-in every N days; null or 0 turns check-ins off. Next check-in is recomputed
context_tagsNoContexts such as Work, Personal, Family, plus custom tags
relationshipNoRelationship label (friend, sister, …). Empty or null clears
relationshipsNoWho they are to the user, primary-first (e.g. Friend + Client)
idempotency_keyNoAlias for request_id.
first_met_locationNoWhere they first met. Null or blank clears
sexual_orientationNoPrivate. Null or blank clears
expected_updated_atNoOptional ISO updated_at you last read. Write applies only if unchanged; otherwise code "conflict" with the current record and changes nothing.
last_interaction_atNoOwner's correction of when they were last in touch (YYYY-MM-DD or ISO date-time with zone; not future). Newer activity still moves it forward.
preserve_old_name_as_aliasNoWhen renaming, keep the previous name as a former_name alias (default true)

Output Schema

NameRequiredDescriptionDefault
hintNoWhere the not_applied fields are changed instead (the Dayze profile).
personYesA Dayze person or contact 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.
is_selfNoTrue when the person is the user's own card (Me).
change_idNoPass to undo_contact_change to revert this change, birthday and birthday_precision included.
provenanceNoWhich connector wrote the record and which connected Dayze account received it.
not_appliedNo
former_name_aliasNoAfter a rename that keeps the old name (preserve_old_name_as_alias, default true): alias, saved, and reason when it could not be kept.
life_state_rebuiltYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedInput schema / properties / context_tags / items / description
      Added value: +"Context tag, e.g. Work."
    • 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."
    • changedInput schema / properties / last_interaction_at / description
      Previous value: -"Owner's correction of when they were last in touch (YYYY-MM-DD or ISO date-time with zone; not future). Saved as owner-set and kept in the contact's history; newer activity still moves it forward."New value: +"Owner's correction of when they were last in touch (YYYY-MM-DD or ISO date-time with zone; not future). Newer activity still moves it forward."
    • changedInput schema / properties / name / description
      Previous value: -"Rename contact (also refreshes URL slug). Prefer this over create+merge for spelling fixes"New value: +"Rename contact (also refreshes URL slug). Prefer over create+merge for spelling fixes"
    • changedInput schema / properties / relationships / description
      Previous value: -"Who they are to the user, in primary-first order (for example Friend + Client)"New value: +"Who they are to the user, primary-first (e.g. Friend + Client)"
    • addedInput schema / properties / relationships / items / description
      Added value: +"Relationship label, e.g. friend."
    • changedInput schema / properties / wallets / description
      Previous value: -"PHI-930: full list of ENS (.eth) / SNS (.sol) names and/or addresses for this contact. Merged into social_handles (legacy ens/ens_address kept); empty array clears wallet keys only."New value: +"ENS (.eth) / SNS (.sol) names and/or addresses for this contact. Merged into social_handles (legacy ens/ens_address kept); empty array clears wallet keys only."
    • addedInput schema / properties / wallets / items / description
      Added value: +"Wallet entry, e.g. {\"name\":\"zzuper.eth\",\"chain\":\"eth\"}."
    • addedInput schema / properties / wallets / items / properties / chain / description
      Added value: +"Chain id, e.g. eth."
  2. Changed4 schema fields changed
    • addedInput schema / properties / company
      Added value: +{
      +  "description": "company. Omit to leave unchanged; null or blank clears.",
      +  "maxLength": 200,
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / email
      Added value: +{
      +  "description": "email. Omit to leave unchanged; null or blank clears.",
      +  "maxLength": 254,
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / occupation
      Added value: +{
      +  "description": "Occupation / job title. Omit to leave unchanged; null or blank clears.",
      +  "maxLength": 200,
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / phone
      Added value: +{
      +  "description": "phone. Omit to leave unchanged; null or blank clears.",
      +  "maxLength": 64,
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  3. Changed11 schema fields changed
    • addedInput schema / properties / address
      Added value: +{
      +  "description": "Postal address (one line). Null or blank clears",
      +  "maxLength": 500,
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / birth_time
      Added value: +{
      +  "description": "HH:MM 24-hour. Null clears",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / cadence_days
      Added value: +{
      +  "description": "Check-in every N days; null or 0 turns check-ins off. Next check-in is recomputed",
      +  "maximum": 3650,
      +  "minimum": 0,
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / death_date
      Added value: +{
      +  "description": "YYYY-MM-DD; marks the contact deceased. Null clears",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / first_met
      Added value: +{
      +  "description": "When/how they first met (free text). Null or blank clears",
      +  "maxLength": 200,
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / first_met_location
      Added value: +{
      +  "description": "Where they first met. Null or blank clears",
      +  "maxLength": 200,
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / gender
      Added value: +{
      +  "description": "Null or blank clears",
      +  "maxLength": 100,
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / is_deceased
      Added value: +{
      +  "description": "false also clears death_date and the memorial reminder",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / last_interaction_at
      Added value: +{
      +  "description": "Owner's correction of when they were last in touch (YYYY-MM-DD or ISO date-time with zone; not future). Saved as owner-set and kept in the contact's history; newer activity still moves it forward.",
      +  "type": "string"
      +}
    • addedInput schema / properties / pronouns
      Added value: +{
      +  "description": "e.g. she/her. Null or blank clears",
      +  "maxLength": 60,
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / sexual_orientation
      Added value: +{
      +  "description": "Private. Null or blank clears",
      +  "maxLength": 100,
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  4. 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"
      +}
  5. Changed3 schema fields changed
    • addedOutput schema / properties / hint
      Added value: +{
      +  "description": "Where the not_applied fields are changed instead (the Dayze profile).",
      +  "type": "string"
      +}
    • addedOutput schema / properties / is_self
      Added value: +{
      +  "description": "True when the person is the user's own card (Me).",
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / not_applied
      Added value: +{
      +  "items": {
      +    "description": "On Me, a profile-mirrored field (name, birthday) that was not saved.",
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  6. Changed1 schema field changed
    • addedInput schema / properties / wallets
      Added value: +{
      +  "description": "PHI-930: full list of ENS (.eth) / SNS (.sol) names and/or addresses for this contact. Merged into social_handles (legacy ens/ens_address kept); empty array clears wallet keys only.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "address": {
      +        "description": "Optional raw 0x or Solana address",
      +        "type": "string"
      +      },
      +      "chain": {
      +        "enum": [
      +          "eth",
      +          "base",
      +          "sol"
      +        ],
      +        "type": "string"
      +      },
      +      "name": {
      +        "description": "ENS or SNS name (e.g. zzuper.eth)",
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  7. Changed1 schema field changed
    • changedInput schema / properties / request_id / description
      Previous value: -"Client idempotency key (retries return original result)."New value: +"Required on personal-write OAuth. Unique for a new write; reuse for an exact retry."
  8. 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"
      +}
  9. Changed1 schema field changed
    • addedOutput schema / properties / change_id
      Added value: +{
      +  "description": "Pass to undo_contact_change to revert this change, birthday and birthday_precision included.",
      +  "type": "string"
      +}
  10. Changed2 schema fields changed
    • changedInput schema / properties / birthday / description
      Previous value: -"YYYY, YYYY-MM, YYYY-MM-DD, or MM-DD / --MM-DD (year unknown). Null/empty clears"New value: +"YYYY, YYYY-MM, YYYY-MM-DD, or MM-DD / --MM-DD (year unknown; 02-29 ok). Null/empty clears"
    • addedOutput schema / properties / former_name_alias
      Added value: +{
      +  "additionalProperties": true,
      +  "description": "After a rename that keeps the old name (preserve_old_name_as_alias, default true): alias, saved, and reason when it could not be kept.",
      +  "type": "object"
      +}
  11. Changed2 schema fields changed
    • addedInput schema / properties / context_tags
      Added value: +{
      +  "description": "Contexts such as Work, Personal, Family, plus custom tags",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / relationships
      Added value: +{
      +  "description": "Who they are to the user, in primary-first order (for example Friend + Client)",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  12. Changed1 schema field changed
    • addedInput schema / properties / preserve_old_name_as_alias
      Added value: +{
      +  "description": "When renaming, keep the previous name as a former_name alias (default true)",
      +  "type": "boolean"
      +}
  13. Changed2 schema fields changed
    • changedInput schema / properties / birthday / description
      Previous value: -"YYYY, YYYY-MM, or YYYY-MM-DD. Null/empty clears"New value: +"YYYY, YYYY-MM, YYYY-MM-DD, or MM-DD / --MM-DD (year unknown). Null/empty clears"
    • addedInput schema / properties / name
      Added value: +{
      +  "description": "Rename contact (also refreshes URL slug). Prefer this over create+merge for spelling fixes",
      +  "type": "string"
      +}
  14. 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"
      +}
  15. 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"
      +    },
      +    "life_state_rebuilt": {
      +      "type": "boolean"
      +    },
      +    "person": {
      +      "additionalProperties": true,
      +      "description": "A Dayze person or contact record.",
      +      "type": "object"
      +    }
      +  },
      +  "required": [
      +    "person",
      +    "changed",
      +    "life_state_rebuilt"
      +  ],
      +  "type": "object"
      +}
  16. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only say readOnly=false, destructive=false, openWorld=false; the description adds substantial context beyond that — omitted fields stay, repeated array entries are no-ops, undo_contact_change(change_id) reverts, requires context.write, share tokens blocked, $0.10 cost, API key required. That is a strong behavioral profile; the only gap is that it doesn't restate conflict/optimistic-locking behavior at this level.

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 mutation verb and target, then ordered by risk: patch semantics, auth/idempotency, revert, permissions, cost. Dense parenthetical style and abbreviations ('ok', 'owner-set') cost a little readability but almost nothing is wasted.

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 29-parameter mutation with an output schema and annotations, the description covers the things an agent must know to call it safely: patch-vs-clear semantics, idempotency/retry, permissions, cost, and the revert tool. Remaining details (per-field formats, conflict code) are fully handled by the schema.

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 29 parameters are already documented in the schema, which sets the baseline at 3. The description adds a few semantic rules the schema does not (full-array replacement for context_tags with idempotent repeats, omitted fields unchanged, last_interaction_at as owner correction), but leaves the other ~26 parameters entirely to the schema.

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+resource ('MUTATES one owned Dayze contact') scoped by person_id, and explicitly contrasts with the sibling undo_contact_change as the revert path. An agent can tell this is the patch tool for an existing owned contact, not a create/identity/alias tool.

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 concrete call conditions: context_tags-only patches are acceptable with the full desired array, last_interaction_at is the owner-set correction path, personal-write OAuth requires request_id, and share tokens cannot write. It stops short of routing the agent among neighbors such as update_person_identity or set_primary_person_name for name/identity changes.

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.