Agni Folio

• Query Account Summary — Returns a high-level summary of the user's portfolio without listing every entry: total net worth in their default currency, breakdown by asset type (stocks, real estate, crypto, etc.), breakdown by currency, breakdown by platform (the institution each holding is custodied at, e.g. 'Phillip Securities Pte Ltd'), total entry count, and entry count per type. Use this for questions like 'what's my net worth', 'how much do I have in stocks', 'what's my asset allocation', and 'how is my money split a
• Add Transaction — Record a transaction (BUY, SELL, DIVIDEND, INTEREST, RENT_INCOME, etc.) on an existing portfolio holding. Find the entry first via query_holdings if the user refers to it by name or symbol. Use only after the user has confirmed. A SIP instalment is a BUY; a mutual-fund switch is a SELL on the source fund and a BUY on the target, never TRANSFER_IN/TRANSFER_OUT.
• Create Investment Plan — Set up a recurring SIP (invest into a mutual fund), STP (transfer money from one fund into another) or SWP (withdraws a fixed amount from the fund each period — it records a SELL of units at each date's NAV) on a schedule. Find the fund(s) with query_holdings first — the target must already be a mutual fund holding in the portfolio (create it with add_portfolio_entry first if it does not exist). For an SWP the target is the fund to withdraw from and there is no source fund. If the plan has insta
• Query Holding By Symbol — Find a single holding by ticker symbol or asset name. Returns the same shape as query_holdings but filtered. Use this when the user references a specific asset ('how much AAPL do I have', 'show me my Apple holding') — cheaper than fetching the full list. ALSO searches inside connected crypto exchanges: a coin held on KuCoin/Binance (spot, Earn, margin, futures wallets) comes back as a row with type EXCHANGE_WALLET_BALANCE, its 'wallet', and 'includedInHolding' naming the exchange lump-sum entry
• Query Recent Trades — Recent executed trades/fills (spot + futures) on your connected exchanges: symbol, side, price, size, fee, time. Read-only, fetched live.
• Query Insurance Summary — Returns the user's insurance summary: total active coverage, total annual premium, count of active policies, and a per-type breakdown (LIFE, HEALTH, VEHICLE, PROPERTY, etc. — count + total coverage per type). Use for 'how much insurance do I have', 'am I covered enough for life', 'what types of policies do I have'. All amounts are already converted to the user's preferred currency, named in the 'currency' field — quote that currency, never another. Policies whose currency could not be converted
• Query Margin Detail — Live cross- and isolated-margin breakdown per coin: total, available, borrowed, interest (accrued and not yet paid — interest already paid is in query_crypto_pnl), and debt ratio. Use for 'how much am I borrowing' or cross-vs-isolated questions. Read-only, fetched live.
• Query User Fire Status — Answer ANY 'when can I retire / what's my FIRE progress / what's my monthly passive income / monthly shortfall' question for THIS user. Pulls net worth from their tracked portfolio and assumptions (annualExpenses, expectedReturn, monthlySavings, withdrawalRate) from their saved preferences. DO NOT ask the user to retype these numbers in chat — use this tool. The model only has to supply current_age. For Lean/Fat FIRE scenarios pass annual_expenses_override (lower = Lean, higher = Fat). If the us
• Query Tokenized Holdings — Lists the user's tokenized-equity holdings — onchain tokens that track a listed share, such as Ondo Global Markets (AAPLon) or Backed xStocks (AAPLx). Returns symbol, name, quantity, price, value, currency and the ISIN of the underlying security, plus whether the user ALSO holds that same security directly through a broker. Use for questions like 'what tokenized assets do I hold', 'do I own NVIDIA twice', or 'how much of my portfolio is onchain equity'. Read-only.
• Delete Transaction — Permanently remove one transaction from a holding's ledger. The holding's quantity and cost basis are recomputed from the remaining transactions and returned, so the effect is verifiable in the same call. SWITCHES: if the row is one half of a fund switch (query_transactions shows a switchGroupId) and the other half still exists, this UNDOES THE WHOLE SWITCH — both the sale of the old fund and the purchase of the new one are removed, and the new fund's holding too if the switch created it. Tell t
• Query Exchange Spot Balances — Per-coin balances on your connected exchanges, broken out by wallet: 'wallet' is SPOT (trade + funding) or EARN (savings/staking products such as PAXG or USDC parked in KuCoin Earn). Breaks the single lump-sum into individual coins. Margin wallets are in query_margin_detail. Read-only, fetched live.
• Switch Fund — Switch money from one mutual fund holding into another fund as ONE event: a sale of the source fund and a purchase of the target, both priced from AMFI's official NAV on the switch date. Use this — never two add_transaction calls, never TRANSFER_IN/TRANSFER_OUT — whenever the user says switch, STP instalment, or moving money between funds. Find the source holding with query_holdings first. Use only after the user has confirmed.
• Add Insurance Policy — Add a new insurance policy to the user's account. Use only after the user has confirmed all the details. The user's MCP client (Claude Desktop / Cursor / etc.) shows a confirmation prompt before this actually runs, so it's safe to invoke once you have all the required fields. Creates a corresponding portfolio entry so the policy shows up in net-worth / insurance views.
• Query Transactions — List the transactions recorded against one holding — id, date, type, quantity, price per unit, amount, fees and notes — newest first, plus the holding's current quantity and total invested. ALWAYS call this before recording or correcting a transaction on an existing holding: cost basis alone cannot tell you what is already there (a dividend reinvest posted without a price adds units at zero cost), so posting blind risks double-counting units the holding already has. Read-only.
• Query Crypto Pnl — Crypto P&L per coin and in total. Unrealized = current value vs cost (amount x recorded avg buy price), where amount includes spot, Earn AND margin positions (held minus borrowed, read live). Also realized P&L from sells, margin interest paid, and allTimePnl = unrealized + realized - interest; historyCoverage says which dates realized/interest cover. Borrowed stablecoins are debt at face value (listed under stablecoins, no P&L). Needs cost basis from recover_crypto_cost_basis or set_crypto_cost_
• Delete Portfolio Entry — Permanently delete a holding from the user's portfolio. This also deletes all transactions associated with the holding. Destructive — the user MUST see and accept the confirmation card before this runs. If the holding carries a 'folio', this removes ONE registrar folio of that fund, not the user's whole position in it — asked to delete a fund held across several folios, name the folios and let the user choose rather than deleting one.
• Query Classification Warnings — Audits the user's holdings for classification problems: entries whose declared type disagrees with what the security catalog knows about their symbol (MISMATCH, with a suggested type), or entries filed under a market-listed type whose symbol cannot be verified at all (UNVERIFIED — often a manual asset like cash or a deposit filed under the wrong type). Use this whenever holdings look inconsistent with their type/category, when the user asks about data quality, or before giving allocation advice
• Query User Coast Fire — Coast FIRE for THIS user: how much they need invested TODAY such that compound growth alone (no further contributions) reaches the FIRE target by their target retirement age. Uses the user's actual portfolio net worth and saved preferences. Returns coastNumberToday, isCoastFired (true if already saved enough to coast), coastShortfall (gap to coast). DO NOT ask the user to retype the numbers — use this tool. Read-only.
• Update User Fire Goals — Update the user's saved FIRE goals — annual expenses, monthly savings, expected return %, withdrawal rate %, and/or FIRE preset (lean / regular / fat). All fields optional — only the ones you pass are updated; others are left as-is. The user will see a confirmation card listing exactly what will change before this runs. Use when the user says things like 'set my expenses to 60k' or 'I save 5k a month now'. Mutating.
• Recover Crypto Cost Basis — Reconstruct the user's crypto cost basis from their KuCoin trade history (~3 months of spot, cross- and isolated-margin fills — as far back as KuCoin keeps them; average-cost method) and record it, together with realized P&L from sells and all margin interest paid (KuCoin keeps interest since April 2023). Overwrites the average cost of coins found in the history. Use when the user asks for P&L / realized or all-time profit / cost basis / 'pull my trade history', or when query_crypto_pnl says rea
• Query Fire What If — Run a hypothetical FIRE projection with explicit inputs — for 'what if I saved more / had more saved already / earned higher returns / had different expenses' style scenarios. ONLY use when the user explicitly proposes hypothetical numbers. For 'when can I retire / what's my current FIRE progress', use query_user_fire_status instead — that one uses their actual tracked data. Returns the same shape as query_user_fire_status. Read-only.
• Set Crypto Cost Basis — Record the user's average buy price (cost basis, in USD) for a crypto coin, so crypto P&L can be computed. Use when the user states what they paid for a coin (e.g. 'my ETH cost basis is 2000'). One value per coin; setting again overwrites it.
• Add Portfolio Entry — Add a new holding to the user's portfolio. Use only after the user has confirmed the addition. The user will see a confirmation card before this actually runs, so it is safe to invoke once you have all the details.
• Compare Tokenized Tax Treatment — Compares how the SAME share is taxed when held as a tokenized wrapper versus bought directly abroad. For Indian residents this is a large difference: a tokenized wrapper is taxed as a Virtual Digital Asset at a flat 30% with no loss set-off, while the direct route via LRS reaches 12.5% on long-term gains. Use when the user asks whether tokenized stocks are worth it, how they are taxed, or which route is better. Informational only, never advice. Read-only.
• Update Transaction — Correct an existing transaction in place. Every argument except transaction_id is optional; only the ones you pass change, the rest keep their current values. Prefer this over delete-and-recreate — recreating breaks the audit trail and can leave the holding empty if the second call fails. Returns the recomputed holding so the effect is verifiable. Use only after the user has confirmed.

Showing the first 25 tools — full list and schemas: Directory API.