well_share_widget

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

Freeze ONE widget's figures and return a link that opens it on its own web page for someone who cannot sign in to Well: an accountant, an investor, a bank, a colleague outside the workspace. Use it when the person asks to send, forward, share or give a link to a figure or table already on screen ("send this cash position to my accountant", "give my bank something to forward"), whether or not they say "link". The figure is already drawn, so this is the whole job: call this tool straight away, with no read of the data first and no question back. For a saved BOARD of several blocks use well_share_canvas instead: a board link freezes every block together. Do not call it when the person only asks about a figure ("is that more than last month?"): nobody asked to send it. To give a link already sent newer figures, use well_refresh_share_link, not this tool: this one makes a new link. HOW: the widget the person is looking at was drawn by one earlier tool call, visible earlier in this conversation. Call no other tool first, not even to re-read the figures. Pass `tool_name` (the tool that drew the widget) and `arguments` (the arguments of that earlier call, copied exactly: the same keys, the same values, nothing added, nothing dropped, no default filled in). Well runs that tool again as the caller and freezes what it returns, on a one-tile board kept with the workspace's boards; the same widget shared again uses the same board. A widget whose tool acted on the workspace (a document, an invoice, an email draft, a company or person as written) is never run again: Well freezes the result that call returned, which it keeps for one day for the person who drew it, in the conversation it was drawn in. Share it from that conversation; another person, another conversation or other arguments find nothing and are refused with `refused_reason: "not_kept"`. This tool has no field for figures. Some widgets (a cash position, burn, runway, cash forecast, cash flow bridge, cost structure, monthly pivot, MRR or category trend card) take the figures themselves as their arguments, because the figures were computed before the card was drawn: Well re-checks those figures and does not measure them again. For those, `arguments` carries the figures, so copy them exactly as the card was drawn and never retype, round, estimate or recompute one. A widget a reader can read can be shared: a figure, a chart, a table, a list, a document, an invoice, an email draft, a record as written. Refused, each with a `refused_reason`: a board (use well_share_canvas); the supplier quote comparison, whose own `url` is a live page for members (give that instead); and a widget that holds nothing for a reader: one that only asks the person something or offers an action (a picker, a choice card, a setup form, next steps, a connect or deploy card), the status of an upload or a connector call, or a removal. Say it cannot be shared by link and why; never offer a link anyway. WHAT THE READER SEES: the widget exactly as the person sees it, private data included (names, salary lines, amounts), at the moment of sharing, with a date: the date its figures were measured when the result states it, otherwise the date the link was made. Never tell the person the figures were measured at that moment. It does not follow the data afterwards. The page is read-only: the reader can change nothing and decide nothing on it. THE LIFETIME: the link has no expiry. It opens as often as the reader likes until the person stops it with well_revoke_share_links, and a refresh does not change that. When the person wants the link to stop at a date, say it opens until they stop it, and offer to stop it when they ask. Give the link to the person who asked in the same reply, with: that it opens until they stop it, that anyone holding the link can read those figures, private data included, and that you can stop it at any time with well_revoke_share_links or give it newer figures with well_refresh_share_link. Do not repeat the figures as if they were the link's content. 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.