update_party
Update customer, vendor, or employee details such as name, currency, notes, active status, or address. Pass only fields to change; returns a diff of what changed.
Instructions
Update a customer's, vendor's, or employee's mutable fields.
None = no change on every parameter; pass an empty
string to clear notes. Returns a diff-style response
with the changed fields only.
Args: party_type: "customer", "vendor", or "employee" (ID counters collide across types — always required). id: Party ID (e.g., "000001"). name: New display name. currency: New ISO currency code (future documents only). notes: New notes; "" clears. Employees have no notes field — rejected, not ignored. active: Set active/inactive (inactive parties hide from default listings but keep their history). address: Full replacement address (see create_party).
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": {
"party_type": "<party_type>",
"id": "<id>"
},
"name": "update_party"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| name | No | ||
| notes | No | New notes value (capped at 4096 characters). Pass ``None`` (default) to leave existing notes unchanged; pass ``""`` to clear. | |
| active | No | ||
| address | No | ||
| currency | No | ||
| party_type | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |