Skip to main content
Glama
moneylover-mcp

moneylover-mcp

Update transaction

moneylover_update_transaction
DestructiveIdempotent

Correct an existing Money Lover transaction by changing its category, amount, note, or date; omitted fields stay unchanged.

Instructions

Correct an existing transaction: change its category, amount, note or date; fields left out keep their current value. Use it only when the user asked for the correction in their own words, after identifying the entry with moneylover_list_transactions (which supplies the id, wallet and date). To remove an entry use moneylover_delete_transaction; to record a new one use moneylover_add_transaction. Use dry_run to preview the before/after while details are unsettled. Behavior: at least one of category, amount, note or new_date is required, and type is only meaningful together with category. id, wallet and date must come from the same moneylover_list_transactions row: Money Lover cannot look up by id alone, so the wallet is searched one day either side of date. The transaction stays in its wallet; to move it to another wallet, delete it and add it again. Photo, location, event, people and the 'exclude from report' flag are kept as they are. Transfers, debts, loans and their repayments are refused because they are linked to other transactions; change those in the Money Lover app. The same limits as moneylover_add_transaction apply: writes are off unless MONEYLOVER_ALLOW_WRITE=true, the wallet allowlist, maximum amount and hourly write limit, and both the current and the new date must fall within 366 days back to 31 days ahead. Repeating the same call changes nothing further. A failure reported as UNCERTAIN means the change may or may not have been saved: check moneylover_list_transactions before retrying.

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": {
      "id": "<id>",
      "wallet": "<wallet>",
      "date": "<date>"
    },
    "name": "moneylover_update_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesId of the transaction, exactly as returned by moneylover_list_transactions.
dateYesThe transaction's current date as YYYY-MM-DD, exactly as returned by moneylover_list_transactions. Used to find it; to move it to another day use new_date.
noteNoNew note, replacing the old one entirely. Pass "" to clear it; omit to keep it.
typeNo"income" or "expense". Only used with category, when that name exists as both.
amountNoNew positive amount in the wallet's currency, e.g. 50000 or "12.50". Omit to keep the current amount.
walletYesName of the wallet the transaction is in, exactly as returned by moneylover_list_transactions.
dry_runNoIf true, find the transaction and validate the change, but do not save it.
categoryNoNew category name as returned by moneylover_list_categories for the transaction's wallet. Sub-categories may be written as "Parent > Child". Omit to keep the current category.
new_dateNoNew date as YYYY-MM-DD. Omit to keep the current date.

Output Schema

NameRequiredDescriptionDefault
afterYesThe transaction as it is (or, for a dry run, would be) after this call.
beforeYesThe transaction as it was before this call.
dry_runYesTrue when nothing was sent to Money Lover.
updatedYesTrue only if the change was really saved.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.0

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond annotations: documents the at-least-one-field rule, type-with-category coupling, the same-row id/wallet/date constraint and one-day-either-side search, that fields like photo/location/people are preserved, that transfers/debts are refused, the write gates and date window, idempotency, and how to handle an UNCERTAIN failure.

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 purpose, then alternatives, then behavior, and nearly every sentence carries non-redundant information. The single dense block runs long, but given the tool's complexity the length is largely justified rather than wasteful.

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?

With an output schema handling return values and annotations covering safety flags, the description fills all remaining gaps an agent needs: prerequisites, write gating, refusal cases, date bounds, idempotency, and failure recovery.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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, but the description adds cross-parameter semantics the per-field schema doesn't state as clearly: the mutual requirement of one of category/amount/note/new_date, type only mattering alongside category, and dry_run's preview behavior.

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 ("Correct an existing transaction") plus the exact fields it can change and the merge semantics ("fields left out keep their current value"). It is unmistakably distinct from add/delete siblings, which are named separately.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly scopes usage ("only when the user asked for the correction in their own words"), mandates the prerequisite lookup via moneylover_list_transactions, and routes alternatives: delete for removal, add for new records, dry_run for previewing unsettled details.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.