Skip to main content
Glama

SwiftProbate

update_asset

Destructive

Update an existing asset's details (name, value, jurisdiction, notes, etc.). Use this instead of creating a duplicate when the user wants to modify an asset.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNoUpdated notes
asset_idYesID of the asset to update
estate_idYesThe estate to act on. Call list_my_estates first to get this id.
asset_nameNoUpdated name for the asset. Use this to correct a typo or add detail the user gave later (e.g. "Jeep Cherokee" → "2018 Jeep Cherokee Latitude Plus"). Renaming edits the existing row — do NOT create a second asset for the same item.
dispositionNoWhat has happened to the asset: 'on_hand' (still in the estate), 'sold', 'transferred', or 'distributed' (given to an heir in kind). Record the sale proceeds as a money-in transaction in the Ledger linked to this asset.
jurisdictionNoUpdated state/jurisdiction
account_numberNoUpdated account/policy/VIN number
estimated_valueNoUpdated estimated value in dollars
has_beneficiaryNoWhether the asset has a named beneficiary
beneficiary_nameNoName of the beneficiary
bypasses_probateNoWhether this asset bypasses probate
date_of_death_valueNoThe asset's value at the date of death (the inventory value used for estate accounting and to compute gain/loss on sale).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources