TrackMyStack

Gets what the portfolio is made of, grouped by sector, region, asset type and currency at once. Use it for concentration and exposure questions — "am I too heavy in tech", "how much of me is in North America", "how much is in cash" - cash is in the Bonds/Cash asset type, though a bank account lands there only if the user classified it so or its name mentions cash, savings or the like (money market, CD, treasury); otherwise it goes by whatever its name suggests, usually Unknown. A holding can be split across buckets, so a global fund counts partly in several regions rather than landing in one. Read portfolios and selection to see what the answer covered. Each holding is classified by what the user said about it, then by what the catalog knows, then by a guess from its name, so "Unknown" means nothing was known rather than nothing was held. totalValue is the positive value classified across the portfolios it covers, including ones kept out of net worth, so it is not net worth. Check isComplete before quoting shares. Needs a TrackMyStack subscription; without one this returns an error, while get_portfolio_overview and list_holdings keep working on closing prices.

get_allocation

Gets dividend income received over a period, payments already declared for the future, and what each holding yields. Use it for "how much did I get in dividends last year", "what is my yield" and "what is coming up". The period defaults to the last twelve months and is always compared against the same number of months immediately before it - or days, when the period is not whole months, so year-to-date reads against the days just before it rather than the same months last year - and a year reads against the year before. Income counts a payment on the day it was paid, converted at that day's rate; upcoming payments are expected rather than received. Yield is always the trailing twelve months over today's value, whatever period is asked for. A holding whose dividends are unknown is left out of it rather than counted as paying nothing, so compare measuredMarketValue against totalMarketValue before calling the figure the portfolio's yield: the part left out could yield more or less. A null yield means unknown, never nothing. Read portfolios and selection to see what the answer covered. Amounts are whole positions, so scale by a portfolio's ownership before reconciling with get_portfolio_overview. Crypto and manually tracked holdings are not covered here at all. Check isComplete before presenting a total as final. Needs a TrackMyStack subscription; without one this returns an error, while get_portfolio_overview and list_holdings keep working on closing prices.

get_dividend_income

Gets the dated positions of one holding, newest first. Use it to answer what was held when, and always before writing a position dated earlier than an existing one: cost basis is computed from the difference between consecutive positions, so inserting one changes what the position after it means. Each entry's quantityChange shows that difference. Results are paginated; use nextOffset while hasMore is true. Needs a TrackMyStack subscription; without one this returns an error, while get_portfolio_overview and list_holdings keep working on closing prices.

get_holding_history

Gets what the account, or one portfolio, was worth over a period and the change across it. The change is in what the account is worth, including money paid in or taken out; it is not an investment return, so say so when the user asks how they are doing. Ask for "endpoints" when only the change matters and a denser granularity when the shape does. Values are end-of-day closes, except a final point dated today, which is priced live and flagged with isLive. Check isComplete before narrating the shape: a point that left a holding out may understate, and a sharp move at such a point is not a real move. Needs a TrackMyStack subscription; without one this returns an error, while get_portfolio_overview and list_holdings keep working on closing prices.

get_net_worth_history

Gets the user's current net worth, the change since yesterday's close, and a per-portfolio breakdown. Every amount carries its currency. Check `isComplete`: when it is false some holdings could not be valued and the totals exclude them — say so rather than presenting the figure as final. The breakdown also lists portfolios the user has kept out of their net worth, named in `portfoliosExcludedFromNetWorth` and flagged per portfolio by `includedInNetWorth`, so the values listed do not necessarily add up to the total. Works without a subscription, in which case net worth is priced at the last market close and today's change is withheld: report `todayChangeUnavailableReason` rather than telling the user nothing moved.

get_portfolio_overview

Gets the holdings with the largest absolute value changes since the previous UTC close, either across net-worth portfolios or within one portfolio. Price change is returned in percentage points and value change always carries its valuation currency. Check isComplete and warnings before presenting the list as the largest movers. Needs a TrackMyStack subscription; without one this returns an error, while get_portfolio_overview and list_holdings keep working on closing prices.

get_movers

Gets the user's savings goals with what each one is worth today and where it lands on its target date. Use it for "am I going to make it" questions rather than valuing the linked portfolios yourself: a portfolio can be split across several goals, and only the allocated share of it counts here. status is decided by the projection, not by progress so far, so a goal at 10% with years left can still be on track - and a goal already past its target date has daysRemaining 0 without status saying so. The projection assumes the contributions keep coming and the return holds; it is arithmetic, not a forecast, so do not present it as what will happen. Check isComplete and the top-level warnings, which cover pricing the linked portfolios, then each goal's own warnings, before quoting its figures. Needs a TrackMyStack subscription; without one this returns an error, while get_portfolio_overview and list_holdings keep working on closing prices.

list_goals

Lists the user's current holdings grouped by portfolio, optionally only some portfolios or some holdings. Values, cost basis and unrealised gain carry explicit currencies; percentage fields are in percentage points. Each figure is the whole position, so scale by the portfolio's ownershipPercent before reconciling with get_portfolio_overview. By default each holding carries what answering a question needs: its home-currency figures only when it is tracked in another currency, and its gross quantity and debt only when it carries debt. Pass detailed true before updating a holding with manage_holdings: only then does a holding carry its revision, the currencies a price and a fee are recorded in, its price quote and its classification. Check each holding's warnings and the top-level isComplete flag before presenting valuations as final. Results are paginated by holding; use nextOffset while hasMore is true. Works without a subscription, in which case every price is the last market close rather than real time - priceLatency says which.

list_holdings

Creates, updates, archives, unarchives, deletes or restores holdings, as each item's operation says. Takes a batch, so a statement can be reconciled in one call; each item is judged on its own and one failing leaves the rest applied - except an empty batch, more than 50 items, or the same holdingId twice, which are refused whole before anything is written. Call list_holdings with includeArchived true before creating a holding that may already exist: an archived one still counts toward value, and a second copy would double it. A position is the total held on a date, not a change, so repeating an update is safe. Repeating a create is not: the server assigns the id and returns it, so a create sent twice makes two holdings — if a create's response was lost, check list_holdings before sending it again. Read get_holding_history first when writing a date that already has later positions after it: cost basis comes from the difference between consecutive positions, so a write between two of them restates the later one, and anything restated comes back in the result for you to tell the user about. Pass that holding's revision - list_holdings with detailed true and get_holding_history both report it - as expectedRevision whenever the change depends on what was already there, and the write is refused rather than applied to state you did not see. Market-linked holdings need a fullTicker from search_market — never guess one — and take their listing's currency. A unit price is in the currency list_holdings reports as priceCurrency (pence for a GBX listing) and a fee in the one it reports as trackingCurrency (pounds); both need detailed true, so read list_holdings that way first when unsure. A price and fee count toward cost basis only on a holding tracked per transaction; each result's notes say when something sent does not count, and costBasisTracking changes how a holding is tracked when the user asks. A write refused because the holding changed since expectedRevision returns the revision it is at now. When the user sold a holding or closed the account it was in, archive it: that records a position of 0 today and archives it, the way the app does, so what it was worth until now stays in net worth history. unarchive only clears the flag and leaves its positions as they are. A create into an archived portfolio is refused; unarchive the portfolio with manage_portfolio first. When a holding is a duplicate or was created by mistake, delete it, which takes it out of net worth history too. A deleted holding can be brought back with restore, once its portfolio is not deleted; anything deleted in an earlier conversation can be restored by the user from the app's "Recently deleted" screen. archive, unarchive, delete and restore take only holdingId and, optionally, expectedRevision. Needs a TrackMyStack subscription; without one this returns an error, while get_portfolio_overview and list_holdings keep working on closing prices.

manage_holdings

Creates, edits, archives, unarchives, deletes or restores one portfolio, as operation says, and returns what it did. create makes an empty portfolio: use it when holdings need to go somewhere that does not exist yet; to add holdings to one the user already has, call list_holdings or get_portfolio_overview for its id instead. The new portfolio is placed after the user's existing ones. The id is assigned by the server and returned; a create repeated after a lost response makes a second portfolio, so check get_portfolio_overview before sending it again. update changes only the settings it is given. Ownership below 100 means the user owns only that share of everything in it, and net worth counts only that share. When the user closed the account or sold everything in it, archive it: each holding in it is recorded as sold today and archived, the way the app archives one, so what it was worth until now stays in net worth history. unarchive clears only the portfolio's own flag; its holdings stay archived until manage_holdings unarchives them. An archived portfolio takes no new holdings until it is unarchived. When the portfolio is a duplicate or was created by mistake, delete it: it and its holdings leave net worth history too. A delete returns the ids of the holdings it deleted with the portfolio; restore brings back the portfolio alone, so then restore those holdings with manage_holdings operation restore. Anything deleted in an earlier conversation can be restored by the user from the app's "Recently deleted" screen. Needs a TrackMyStack subscription; without one this returns an error, while get_portfolio_overview and list_holdings keep working on closing prices.

manage_portfolio