Skip to main content
Glama

Share a widget by link

well_share_widget

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. A request for a link that someone else opens (« lien de partage », a link for the accountant or the bank) is a share: call this tool, and Well asks the person to confirm the link. A link that someone else opens is a share, made by well_share_widget, not the file of the PDF-asked line. For the cash or the runway, a share needs the card of that figure: when none is in the conversation, load the figure's skill (cash-position, or runway), follow it to its card, then call well_share_widget. NEVER say that Well cannot share the cash or the runway by link. A link to share is never a button: write one sentence that says what it is, then the link under it. A link Well sends under your text already has its sentence: never write it again. 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. Search for well_share_widget when it is not loaded.

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. For a card the person is looking at, call well_share_widget with that card's tool and arguments. 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.

Input Schema

NameRequiredDescriptionDefault
argumentsYesThe arguments of that earlier call, copied exactly: no field added, none dropped, no default filled in. Never figures typed by hand.
tool_nameYesThe tool that drew the widget, for example well_render_cash_position.
workspace_idNoTarget workspace. Omit when the token authorizes one workspace. Required when it authorizes several — a write lands in exactly one workspace and this call would not say which.
conversation_idNoThe conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation.
idempotency_keyNoOptional client-supplied key. A retried write with the same key returns the original result instead of re-applying the operation.
workspace_scopeNoRestrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace.

Output Schema

NameRequiredDescriptionDefault
urlNoThe link to give the person who asked. Later, well_list_share_links gives it back to them only.
nameNo
errorNo
successYes
expires_atNoNull: the link opens until it is stopped.
computed_byNo"caller" when the figures were computed before the card was drawn and Well only re-checked them, "server" when Well measured them.
resolved_atNoWhen the link was made. For a widget with figures computed beforehand, this is not when they were measured.
share_link_idNoNames this link for well_refresh_share_link and well_revoke_share_links. Not something to give the reader.
canvas_view_idNoThe one-tile board the link was taken from.
refused_reasonNo
conversation_idNoThe conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
newly_connectedNoTools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later.
resolved_workspaceNoThe workspace that answered, when the caller named none and the token authorizes several.
conversation_id_noteNoPresent only when the server opened a fresh lane, stating that no choice recorded earlier was read.
conversation_id_sourceNoWhere the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedOutput schema / properties / resolved_workspace / properties / name / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / resolved_workspace / properties / name / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. Changed1 schema field changed
    • changedOutput schema / properties / url / description
      Previous value: -"The link to give the person who asked. Returned once and never again."New value: +"The link to give the person who asked. Later, well_list_share_links gives it back to them only."
  3. Changed3 schema fields changed
    • removedInput schema / properties / expires_in_days
      Removed value: -{
      -  "description": "Days until the link stops opening. Omit for 30.",
      -  "maximum": 30,
      -  "minimum": 1,
      -  "type": "integer"
      -}
    • changedOutput schema / properties / expires_at / description
      Previous value: -"When the link stops opening."New value: +"Null: the link opens until it is stopped."
    • changedOutput schema / properties / expires_at / type
      Previous value: -"string"New value: +"null"
  4. Changed10 schema fields changed
    • changedInput schema / properties / expires_in_days / description
      Previous value: -"Days until the link stops opening. Omit for 7."New value: +"Days until the link stops opening. Omit for 30."
    • removedInput schema / properties / max_opens
      Removed value: -{
      -  "description": "How many times the link opens. Omit for 20.",
      -  "maximum": 200,
      -  "minimum": 1,
      -  "type": "integer"
      -}
    • addedOutput schema / properties / canvas_view_id
      Added value: +{
      +  "description": "The one-tile board the link was taken from.",
      +  "type": "string"
      +}
    • removedOutput schema / properties / collapsed_salary_lines
      Removed value: -{
      -  "maximum": 9007199254740991,
      -  "minimum": -9007199254740991,
      -  "type": "integer"
      -}
    • addedOutput schema / properties / expires_at / description
      Added value: +"When the link stops opening."
    • removedOutput schema / properties / max_opens
      Removed value: -{
      -  "maximum": 9007199254740991,
      -  "minimum": -9007199254740991,
      -  "type": "integer"
      -}
    • addedOutput schema / properties / name
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / properties / refused_reason / enum
      Previous value: -[
      -  "writes",
      -  "worklist",
      -  "settings_or_access",
      -  "personal_detail",
      -  "use_board_link",
      -  "salary_not_reducible"
      -]New value: +[
      +  "writes",
      +  "use_board_link",
      +  "other_workspaces",
      +  "no_share_value",
      +  "use_live_member_link",
      +  "not_kept",
      +  "one_result"
      +]
    • changedOutput schema / properties / share_link_id / description
      Previous value: -"Names this link for well_revoke_widget_shares. Not something to give the reader."New value: +"Names this link for well_refresh_share_link and well_revoke_share_links. Not something to give the reader."
    • removedOutput schema / properties / tool_name
      Removed value: -{
      -  "type": "string"
      -}
  5. Changed1 schema field changed
    • changedOutput schema / properties / newly_connected / description
      Previous value: -"Tools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. Start the reply with one line per entry, in the person's language: \"<name> is connected.\". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later."New value: +"Tools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: \"<name> is connected.\". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later."
  6. Changed1 schema field changed
    • addedInput schema / properties / workspace_scope
      Added value: +{
      +  "description": "Restrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace.",
      +  "enum": [
      +    "family"
      +  ],
      +  "type": "string"
      +}
  7. Added

TDQS

A4.7/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only mark this as a non-destructive, non-open-world write; the description adds far more: no expiry, anyone holding the link sees private data, the page is read-only, the snapshot does not follow later data, action-only widgets are refused with a refused_reason, and stale/non-kept snapshots for mutating tools fail with refused_reason: "not_kept". Nothing contradicts the annotations, and revocation/refresh paths are named.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Core purpose and triggers are front-loaded, but the text is very long for a tool definition and repeats the exact-copy rule for arguments several times. Some passages are reply-formatting instructions to the model ('write one sentence that says what it is, then the link under it') that sit awkwardly next to tool semantics.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter tool with nested arguments and an output schema, the description covers what an agent needs: prerequisite that the widget already exists in the conversation, allowed vs refused widget kinds, workspace scoping, and the user-facing obligations after the call. Return values are left to the output schema, which is appropriate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so parameter documentation is already handled structurally. The description still adds operational meaning: tool_name must be the tool that drew the widget, arguments must be copied exactly with no retyping of figures, and workspace_id is only needed when the token authorizes multiple workspaces. It does not say anything extra about conversation_id or idempotency_key, which the schema covers.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource and scope: 'Freeze ONE widget's figures and return a link that opens it on its own web page'. It explicitly separates itself from well_share_canvas (boards) and well_refresh_share_link (newer figures for an existing link), so an agent can pick it without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete trigger utterances ('send this cash position to my accountant'), an explicit exclusion ('Do not call it when the person only asks about a figure'), and named alternatives for boards and refreshes. It also covers non-English phrasing and the card-loading prerequisite for cash/runway.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources