Whisper Money

Delete a budget, with its periods and their spending history. The transactions themselves are untouched — only the budget that was watching them goes away.

delete_budget

Delete a category, uncategorizing its transactions. strategy decides its children: "reparent" (default) lifts them to its parent, "promote" makes them roots, "cascade" deletes the subtree too.

delete_category

Delete a label. It is removed from every transaction it was attached to.

delete_label

Delete a manually-created transaction. Only manual transactions can be deleted; bank/imported ones cannot, and neither can one part of a split.

delete_transaction

The app's full cashflow picture for a date range: income/expense/savings/investment summary (current vs previous), the category flow sankey and the monthly trend. Covers the whole account.

get_cashflow

Net worth for a date range: the current total vs the previous period, plus each account's balance evolution. Set granularity to "monthly" (default) or "daily". Covers the whole account.

get_net_worth

Add and/or remove labels on any transaction, including bank/imported ones. Pass add_label_ids and/or remove_label_ids.

label_transaction

List the user's accounts in a space and whether each is bank-connected. Bookkeeping records only: no tool moves money between them or to anyone; the user does that at their bank.

list_accounts

List the user's medals: the ones earned, the next rung to aim at on each track with how far along they are, and the ones beyond it, which stay nameless. Plus the unlocked count and saving streak.

list_achievements

List the user's automation rules in a space, lowest priority number first. Use the ids with update_automation_rule, delete_automation_rule and apply_automation_rule.

list_automation_rules

List the user's budgets with the current period's allocated, spent and remaining amounts, plus the categories and labels each one tracks. Covers the whole account.

list_budgets

List the user's categories in a space. Categories form a tree via parent_id; use the ids to filter search_transactions or spending_by_category.

list_categories

List the user's labels in a space. Use the ids with label_transaction or automation-rule label actions.

list_labels

List the spaces the user can access (personal and shared). Pass a space id to the other tools' `space` argument to query a specific one.

list_spaces

Merge a split back into the single transaction it came from. Pass any one of its parts. The category, labels and notes on every part are lost.

merge_transaction_splits

Search and filter the user's transactions by text, category, account, label, date range and amount. Use it to analyse spending, or to find recurring charges by grouping results by merchant.

search_transactions

Expense spending rolled up by category for a date range, across the user's whole account. Without parent_category_id it returns root categories; pass one to drill into its children.

spending_by_category

Split one transaction into 2-20 parts, each with its own category and labels. Works on bank transactions too. The parts must add up to the original and all move money the same way.

split_transaction

Edit an account: name, type, currency, bank, ownership share and the loan/property details. Only the fields you pass change. On a bank-connected account only the name and ownership can change.

update_account

Edit an automation rule. Only the fields you pass are changed. The rule must always keep at least one action (a category or labels). See create_automation_rule for the rules_json format.

update_automation_rule

Rename a budget or change its limit; only the fields you pass are changed. Its period length, start day, rollover and tracked categories are fixed — delete and recreate it to change those.

update_budget

Edit a category. Only the fields you pass are changed. Moving it under a parent (or clearing parent_id to make it a root) re-derives its type/cashflow and cascades the type to its descendants.

update_category

Edit a label. Only the fields you pass are changed.

update_label

Edit a transaction; only the fields you pass change. Notes and category work on any transaction, bank/imported ones included; the other fields only on manually-created ones.

update_transaction