Step 1 of 3. Submits the username and returns the security question BG asks for. Relay that question to the user, then call bg_login_answer with their answer and password. The login expires after 5 minutes if not completed.

Step 2 of 3. Completes the login with the security answer and password. Returns { status: "authenticated" } on success, or { status: "otp_required" } if BG sends a one-time code — in that case ask the user for the code and call bg_login_otp.

Step 3 of 3, only needed when bg_login_answer returned status "otp_required". Submits the code Banco General sent to the user.

Reports whether there is a usable Banco General session, who it belongs to, and how fresh it is. Verifies against the bank rather than trusting the stored session file. Call this before asking the user for credentials — they may already be logged in. If it reports authenticated: false, log in before answering anything about the accounts; the data tools have nothing to read and will fail.

Deletes the stored session and any credentials kept in the Keychain, and closes any login in progress.

Lists every Banco General product on the dashboard — savings accounts, credit cards and the Pro-Futuro pension — with balances and the portalId other tools need. Start here. Balances are as of BG's lastSyncDate, not live.

Full detail for one product, dispatching on its type: savings accounts return balances, associated debit cards and pending purchases ("Compras en proceso"), credit cards return limit/cutoff/payment dates, and the pension returns fund balances. Get the portalId from bg_list_accounts.

Transactions for one savings account over a date range, with pagination handled internally. Dates are Panama local time. Also returns pending purchases ("Compras en proceso") — accepted but not yet posted. They are already out of the available balance, and are reported separately because they are not movements yet. For credit-card charges use bg_list_card_transactions.

Charges and payments on a credit card for a statement period. Pass month/year for a specific period, or omit both for the current one. A BG statement period is not a calendar month — it runs from the previous cutoff date — so set clampToMonth to restrict results to the calendar month.

Statement for a credit card: balance, minimum payment, cutoff and due dates, credit plans and rates. Pass month/year for a past statement, or omit both for the current period. Also returns the history of past cutoff dates so you can pick another period.

Banco General's own spend-by-category breakdown for a card statement period (Comida y Bebida, Transporte, Supermercados, etc.), with transaction counts and totals. Omit month/year for the current period. This is the bank's categorization, not a computed one.

Balances and fund breakdown for the Pro-Futuro pension product, plus the monthly statement (contributions, interest, commissions, withdrawals) when month and year are given.

Searches every savings account and credit card at once over a date range, optionally filtering by description text and amount. Use this for questions like "how much did I spend at X" or "find that $250 charge in March" — it saves calling the per-account tools one by one. Covers pending purchases ("Compras en proceso") as well as posted movements, so a charge made today is findable; those come back with source "pending".

Aggregates every account for a month (or an explicit date range): total income, total spending, net, a per-account breakdown and the largest transactions. Use this for "how did I do this month".