Skip to main content
Glama

SwiftProbate

update_transaction

Destructive

Correct an existing ledger transaction when the user wants to fix a mistake — a wrong amount, date, category, payee, who paid, or which heir/asset it relates to. Find the transaction's ID with get_transactions first. This is a PARTIAL update: pass transaction_id plus ONLY the fields that change; everything you omit is left as-is. Use this (not a new correcting entry) whenever the user says an amount or detail was wrong. Confirm the correction with the user before calling.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNoChange the free-text note.
amountNoChange the positive dollar amount.
heir_idNoChange the related heir ID (for distributions).
paid_byNoChange who paid (disbursements). 'individual' means a person paid out of pocket and is owed reimbursement.
asset_idNoChange the related asset ID.
categoryNoChange the category. Must belong to the transaction's direction (same taxonomy as log_transaction).
directionNoChange the direction. If you change this, also pass a matching category.
estate_idYesThe estate to act on. Call list_my_estates first to get this id.
payer_nameNoWhen paid_by='individual' AND someone other than the user paid, the person's name. Omit if the user themselves paid.
transaction_idYesID of the transaction to update (from get_transactions).
payee_or_sourceNoChange who was paid (money out) or the source (money in).
transaction_dateNoChange the date, as YYYY-MM-DD.

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