well_get_cash_flow_bridge

io.github.WellApp-ai/well-mcp · Verify this server

Get the workspace's cash-flow bridge — how the opening cash position became the closing one — the exact same steps the Well app's cash-flow waterfall chart shows. Use this instead of deriving flows from raw transaction reads. Returns `steps` in render order, each `{ label, value, kind }`. `kind` says how to read `value`: - "start" and "total" carry an ABSOLUTE cash position (the opening and closing anchors). - "increase" and "decrease" carry a gross flow MAGNITUDE, always positive. The direction lives in `kind`, not in the sign — never report a "decrease" as a negative number or add the magnitudes as though they were signed. This is a SELF-CONTAINED reconciliation: the "start" and "total" steps ARE the opening and closing balances for the period, so do not also call `well_get_cash_position` to fetch them. That tool answers a different question — the balance right now — and pairing it with this one reports today's figure beside last period's bridge as though they were the same reading. An EMPTY `steps` array means neither anchor could be measured (nothing connected, or the reads timed out). That is missing data, NOT a month with no movement — say the bridge is unavailable rather than reporting flat cash. Pass `year` + `month` to bridge a past period instead of the live window. This is not a decomposition of `well_get_cost_structure`: this reconciles opening to closing cash across inflow and outflow, while cost structure splits a single month's outflow by category. They will not tie out, and presenting one as the breakdown of the other is wrong. If `hints` are present (excluded accounts, an FX gap, or an unexplained residual between the anchors and the flows), disclose them rather than presenting the bridge as balanced. Call this directly — no other tool call is needed first (workspace is resolved from the caller's authorized token, same as every other well_* tool).