well_render_monthly_pivot

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

Put a table of amounts per company and per month onto the monthly-pivot card: one row per company with its logo and name, an optional category column, then one column per month. The running month is drawn apart, at the end, marked as in progress. **This tool measures nothing.** Pass a pivot another tool measured, as it is: for subscriptions, the `pivots` entry of `well_measure_subscriptions` for the currency you drew the trend in. Never build or edit the rows yourself. The server reads the running month from its own clock, in UTC, and draws the `month_count` complete months before it (12 by default). It resolves each row's company from `company_id`, so the card shows the company's logo and name. A row with a null `company_id` and a `label_means_id` is a bank label tied to no company: it is drawn from its `name`. A payee the company read cannot reach is drawn from the `name` and `domain` on its row, as the measure returned them. A row with a null `category` is drawn as uncategorised. REFUSED rather than drawn: - more than 50 rows, or two rows for one company or one label - a row with both or neither of `company_id` and `label_means_id`, or a label row with no `name` - an amount keyed outside the drawn months, or keyed by anything but `YYYY-MM`, or a negative amount. A measure that ran just before the month changed is refused on its oldest month: run it again - a `company_id` this workspace cannot read and whose row carries no `name` (`success: false` names the ids) - a `currency` outside ISO-4217 A month with no amount draws an empty cell, which reads as "no payment", never as zero. When the token authorizes one workspace, call this directly — no workspace call is needed first. When it authorizes several, this read will not guess which one you mean: pass `workspace_id` on the call.