allocate_funds
ChatGPTMoves money toward a savings goal by changing how much it holds. amount is added, and a negative amount withdraws. This only tracks the goal — it records no transaction and moves nothing between accounts. Requires an active subscription.
bulk_update_transactions
ChatGPTUpdate several existing transactions at once — recategorise, append notes, or correct amounts/dates across many rows in one call. Pass EVERY change via updates — never call this once per transaction, or the user gets one confirmation card per row instead of one for the batch. The account balance and each category's occurrence count are recalculated together, atomically. Requires an active subscription. Two-step and server-enforced: call first WITHOUT confirmationToken and nothing is written — you get back the current and resulting rows plus a short-lived confirmationToken; the confirmation binds the whole batch, so the second call takes no arguments but that exact token. IMPORTANT: if this tool returns status "preview", tell the user you prepared the preview. Do NOT say the operation was blocked or failed.
create_receipt_expenses
ChatGPTTHE tool for a shop receipt — a paragon, a till or cash-register slip, a photographed or scanned bill, an itemised order. Use it for ANY request to add, split, categorise or book a receipt ("podziel ten rachunek na kategorie i dodaj do wydatków", "add this receipt split by category"), including when you have already read every line off the photo and worked out the split yourself — that is exactly the input this tool wants. Never book receipt lines with create_transaction or create_transactions instead: only this tool reconciles against the printed total, shows the user the split before anything is written, and collapses the lines into one transaction per category. Send EVERY line as a separate item with its own name and amount; send discount or rabat lines as NEGATIVE amounts. Items are then summed per category and stored as one transaction per category, so a 45-line receipt becomes a handful of rows. purchasedAt is REQUIRED and is the date AND time PRINTED ON THE RECEIPT as a plain wall clock, "2026-09-17T17:20" — never append Z and never convert it yourself. Read the time off the receipt: on a Polish paragon fiskalny it is printed next to the date in the footer (e.g. "2026-09-26 09:39" beside the print number), and again on the card-payment slip. A date without the time, or no purchasedAt at all, is rejected — never substitute noon or the current time; pass the shopper's IANA timeZone separately when you know it. total is the printed SUMA and is only used to reconcile. Leave categoryId null on any item you are unsure about — the server fills it in from this project's own history, which is more reliable than guessing. Before categorizing, call list_categories to fetch this project's expense categories. Explicit user/model assignments take priority over history. Corrections must resend the COMPLETE corrected receipt and produce a fresh preview; never reuse an earlier token after corrections. Approval may come from the widget or chat: chat approval must use the most recent reviewed token. Unassigned items and non-positive category totals prevent confirmation until corrected. Requires an active subscription. Two-step and server-enforced: call first WITHOUT confirmationToken and nothing is written — you get the per-category breakdown and a short-lived confirmationToken. Show that breakdown, wait for the user's explicit approval, then call again with that exact token. IMPORTANT: if this returns status "preview", say you prepared the breakdown — do NOT say it was blocked or failed, and never claim the expenses were added until status is "saved".
create_recurring_transaction
ChatGPTCreate a recurring payment rule (a subscription, rent or other repeating bill), typically one found by detect_recurring_patterns. Only call it after the user has explicitly asked to automate that payment. The rule starts today and repeats every intervalCount intervalUnit (e.g. 1 month). With autoAdd true the app books each occurrence as a transaction on its due date, starting today; with autoAdd false it only reminds the user. amount is a positive number and isExpense must match the category from list_categories. The rule can be edited or removed later in the Finanse app. Requires an active subscription.
create_transaction
ChatGPTRecord ONE expense or income the user already made, from a single amount they state. NOT for a shop receipt: a paragon, till slip, photographed or scanned bill or itemised order goes to create_receipt_expenses even when you have already read its lines and worked out the split yourself. amount is a positive number. The direction (expense or income) is taken from the chosen category, so pick the right categoryId from list_categories. date is the wall clock exactly as a person reads it ("2026-09-17T17:20") — never append Z and never convert it yourself; pass the IANA timeZone separately when you know it, otherwise Warsaw is assumed. Always include the time when you know it; a date alone is booked at 12:00. It defaults to now. accountId defaults to the project default account. Requires an active subscription. IMPORTANT: the transaction is stored ONLY if this tool returns status "saved" with the resulting transaction. If you get an error, no result, or the turn is interrupted before that arrives, nothing was recorded — say so and retry. Never tell the user it was added without that confirmation, and report the amount and category name exactly as returned.
create_transactions
ChatGPTRecord several unrelated expenses or incomes the user already made, in one call — never call create_transaction once per row when you already know the whole set. NOT for a shop receipt: one paragon, till slip, photographed or scanned bill or itemised order split across categories is create_receipt_expenses, which reconciles against the printed total and has the user approve the split first; reach for it even when you have already read the lines and worked out the split yourself. Each item works like create_transaction: the direction follows its categoryId, date is the wall clock exactly as a person reads it ("2026-09-17T17:20", never append Z) — always include the time when you know it (a date alone is booked at 12:00), and accountId defaults to the project default account. Requires an active subscription. IMPORTANT: the transactions are stored ONLY if this tool returns status "saved" with every resulting row. If you get an error, no result, or the turn is interrupted before that arrives, nothing was recorded — say so and retry. Never tell the user they were added without that confirmation.
delete_transaction
ChatGPTPermanently delete one or more transactions and revert their effect on the account balance. This cannot be undone. Pass EVERY id you intend to remove in a single call via transactionIds — never call this once per transaction, or the user gets one confirmation card per row instead of one for the batch. Requires an active subscription. Two-step and server-enforced. Call it first WITHOUT confirmationToken — nothing is modified and you get back the real stored transaction, the resulting state and a short-lived confirmationToken. Show that preview to the user, wait for their explicit approval, then call again with the identical arguments plus that exact token. The token cannot be guessed or reused for different arguments, so a call without it never writes. IMPORTANT: if this tool returns status "preview", tell the user you prepared the preview. Do NOT say the operation was blocked or failed.
detect_recurring_patterns
ChatGPTAnalyzes recent transactions (last 90 days) to detect potential recurring subscriptions or bills that are not yet automated. Use this to suggest automating them.
find_transactions
ChatGPTSilent, filtered transaction lookup for your own reasoning — the user sees no card. Use it for every task that only needs rows as data: recategorising, finding ids to update or delete, duplicates, counting, totals for a merchant, checking which rows match a rule. Filters combine with AND; queries match notes (any term). Dates are calendar days in the project's time zone, inclusive. At most 500 rows, newest first; truncated=true means narrow the filters or split the range. Never follow it with list_transactions or search_transactions unless the user asks to see the rows.
get_balance_history
ChatGPTDaily total balance points for the last 30 days, oldest first.
get_budget_status
ChatGPTHow each expense category stands against its monthly budget: amount spent, the limit in force that month, percent used and whether it was met or exceeded. Pass every month you need in a single call via periods — up to 12 — each one comes back as its own group. Never call this once per month. Members with restricted visibility cannot read budgets.
get_monthly_stats
ChatGPTSilent lookup, renders nothing. Per month: income, expense and net totals, every category's total and share, and — for expense categories — the budget limit in force that month, percent used and verdict. Use it to reason, compare months or answer a question in words; use show_monthly_summary or show_budget_status only when the user asks to see a card. Pass every month in one call via periods (up to 12). Budget fields are null for members who cannot see budgets.
get_monthly_summary
ChatGPTAggregated totals per category for one or more calendar months, plus overall income, expense and net totals per month. Prefer this over list_transactions when only totals are needed. Pass every month you need in a single call via periods — up to 12 — each one comes back as its own group. Never call this once per month.
get_project_overview
ChatGPTGet the current state of the user's finance project: accounts with balances, total balance, member count, date of the oldest transaction and total transaction count. Amounts are numbers in the project currency, returned as project.currency. Call this first to orient yourself.
get_receipt_status
ChatGPTWidget-only: whether the receipt booked on this account at this printed moment is already saved, with its saved rows.
get_safe_to_spend
ChatGPTCalculates the safe-to-spend amount based on current balance minus upcoming bills until the end of the month.
get_savings_goals
ChatGPTReturns every savings goal in the current project with its target, what is put aside so far and the progress percentage. Amounts are unsigned and in the project currency.
get_transactions_state
ChatGPTWidget-only: the stored state of the transactions a confirmation card previews, so the card can tell whether its change was already applied.
get_upcoming_transactions
ChatGPTList the payments the project's recurring rules will produce between startDate and endDate (both YYYY-MM-DD, inclusive), in date order. Use it to answer what bills are coming up before a given date. It only projects existing rules — nothing is recorded.
list_accounts
ChatGPTSilent lookup, renders nothing. The project's accounts (id, name, balance, isDefault) plus today's date and time zone. Call it before a write only when the user names an account ("z konta Alior") or a relative date needs today; otherwise writes use the default account. transfersOnly accounts (savings, emergency fund) never take expenses or incomes. Use show_project_overview only when the user asks to SEE their accounts.
list_categories
ChatGPTList the project's transaction categories. isExpense=true means the category holds expenses, false means income. Use category ids when creating or updating transactions.
list_debts
ChatGPTSilent lookup, renders nothing. Loans, cards, BNPL and private debts the household entered in the app, with the payoff plan saved there (snowball or avalanche + extra monthly amount). balance is an estimate for today (fixed rate, no fees, insurance or overpayments) — say so, never present it as the bank balance. payoffMonth is YYYY-MM with the saved plan; null = never paid off at this payment within 600 months. includeInPlan=false debts pay their own schedule and are left out of the totals. Read-only: never offer to add or change a debt (the user does it in the app), and never give refinancing or consolidation advice.
list_life_events
ChatGPTLife events the household marked in the app — a move, a new job, a birth, a death in the family, a job loss. Read-only context for explaining why spending or income changed; never ask the user to describe these, and never add them (the user enters them in the app). An event with endDate null is a one-off change that still applies from startDate on. Dates are YYYY-MM-DD, inclusive; omit both to get every event.
list_projects
ChatGPTList every finance project the user belongs to, with its id, currency, the user's role, member count and total balance. isCurrent marks the project every tool uses when projectId is left out. Call this when the user names another project or asks about all of their projects, then pass that project's id as projectId to the other tools.
list_transactions
ChatGPTRenders a card listing every row to the user. Call it ONLY when the user explicitly asks to see, show or list transactions. To count, analyse, match or collect ids for update_transaction, bulk_update_transactions or delete_transaction, use find_transactions instead — it renders nothing. List every transaction for one or more calendar months, newest first within each month. Pass every month you need in a single call via periods — up to 12 — and each one comes back as its own group, in the order given. Never call this once per month. Amounts are unsigned numbers; the sign is derived from isExpense.
search_transactions
ChatGPTRenders a card listing every row to the user. Call it ONLY when the user explicitly asks to see, show or list transactions. To count, analyse, match or collect ids for update_transaction, bulk_update_transactions or delete_transaction, use find_transactions instead — it renders nothing. Full-text search across transaction notes (case-insensitive substring match), newest first. Pass every term you want in a single call — up to 10 — and each one comes back as its own group, in the order given, including the terms that matched nothing. Never call this tool once per term. Across all groups at most 200 transactions are returned, shared evenly between the terms; a group's truncated=true means it had more.
show_balance_history
ChatGPTRenders a card in the chat. Call it only when the user asks to see this, at most one card per reply, and never just to look something up. The card is the answer: do not re-list its contents, add at most one short sentence. Shows the daily total balance for the last 30 days as a chart. Only when the user asks how their balance moved.
show_budget_status
ChatGPTRenders a card in the chat. Call it only when the user asks to see this, at most one card per reply, and never just to look something up. The card is the answer: do not re-list its contents, add at most one short sentence. Shows how each expense category stands against its monthly budget: spent, the limit in force that month, percent used, met or exceeded. Pass every month in one call via periods — up to 12 — never one call per month. For numbers you only need to reason with, use get_monthly_stats. Members with restricted visibility cannot read budgets.
show_monthly_summary
ChatGPTRenders a card in the chat. Call it only when the user asks to see this, at most one card per reply, and never just to look something up. The card is the answer: do not re-list its contents, add at most one short sentence. Shows per-category totals and shares plus income, expense and net for one or more calendar months — the card for "where did my money go". Pass every month in one call via periods — up to 12 — never one call per month. For numbers you only need to reason with, use get_monthly_stats.
show_project_overview
ChatGPTRenders a card in the chat. Call it only when the user asks to see this, at most one card per reply, and never just to look something up. The card is the answer: do not re-list its contents, add at most one short sentence. Shows the accounts with balances, the total balance, member count and transaction count. Only when the user asks to see their accounts, balances or the overall state. Never before a write and never for ids or today's date — that is list_accounts.
show_recurring_suggestions
ChatGPTRenders a card in the chat. Call it only when the user asks to see this, at most one card per reply, and never just to look something up. The card is the answer: do not re-list its contents, add at most one short sentence. Detects payments that repeated over the last 90 days (subscriptions, bills) and are not yet a recurring rule. Only when the user asks what repeats or what could be automated; turn one into a rule with create_recurring_transaction only after the user picks it.
show_safe_to_spend
ChatGPTRenders a card in the chat. Call it only when the user asks to see this, at most one card per reply, and never just to look something up. The card is the answer: do not re-list its contents, add at most one short sentence. Shows how much is safe to spend until the end of the month: the current balance minus the recurring bills still due this month, plus incomes still due. Only when the user asks how much they can still spend or whether they can afford something this month.
show_search_results
ChatGPTRenders a card in the chat. Call it only when the user asks to see this, at most one card per reply, and never just to look something up. The card is the answer: do not re-list its contents, add at most one short sentence. Rows go to the card only — you get counts, not rows. To count, analyse, match or collect ids for update_transaction, bulk_update_transactions or delete_transaction, use find_transactions instead — also when your client shows no cards. Case-insensitive search of transaction notes, newest first. Pass every term in one call — up to 10 — each comes back as its own group in the order given, including terms that matched nothing. Never one call per term. At most 200 rows across all groups, shared evenly; a group's truncated=true means it had more.
show_transactions
ChatGPTRenders a card in the chat. Call it only when the user asks to see this, at most one card per reply, and never just to look something up. The card is the answer: do not re-list its contents, add at most one short sentence. Rows go to the card only — you get counts, not rows. To count, analyse, match or collect ids for update_transaction, bulk_update_transactions or delete_transaction, use find_transactions instead — also when your client shows no cards. Lists the transactions of one or more calendar months, newest first. Pass every month in one call via periods — up to 12 — never one call per month.
show_upcoming_transactions
ChatGPTRenders a card in the chat. Call it only when the user asks to see this, at most one card per reply, and never just to look something up. The card is the answer: do not re-list its contents, add at most one short sentence. Shows the payments the project's recurring rules will produce between startDate and endDate (YYYY-MM-DD, inclusive), in date order. Only projects existing rules — records nothing. Only when the user asks what bills or payments are coming.
simulate_savings_timeline
ChatGPTCalculates how many months it takes to reach a target amount at a given monthly contribution. Pure arithmetic — it reads and changes nothing.
update_transaction
ChatGPTUpdate fields of an existing transaction. date is a plain wall clock ("2026-09-17T17:20"), never Z; pass timeZone alongside it when you know it. The account balance is recalculated automatically — the expense/income direction always follows the category, so change categoryId to flip it. Requires an active subscription. Two-step and server-enforced. Call it first WITHOUT confirmationToken — nothing is modified and you get back the real stored transaction, the resulting state and a short-lived confirmationToken. Show that preview to the user, wait for their explicit approval, then call again with the identical arguments plus that exact token. The token cannot be guessed or reused for different arguments, so a call without it never writes. IMPORTANT: if this tool returns status "preview", tell the user you prepared the preview. Do NOT say the operation was blocked or failed.