Well

Switch workspace

well_switch_workspace

Write this conversation's context: the one place its standing choices live. This is the tool the widget cards call when the user CLICKS them: the workspace pin and queue, the selected months, the selected counterparties, and the step acknowledgements are all recorded here, and every later tool call defaults to them.

Pass any of:

workspace_ids (ordered list): the workspaces to work in. The FIRST entry becomes the pin and the rest the workspace_queue to work through next. Every id must be one this connection is already authorized for — call well_list_workspaces to see them. This grants no new access; it only chooses among the authorized workspaces.
periods: the months the user VALIDATED on the period card ({ calendar_year, calendar_month } each). Period-scoped reads (well_list_missing_invoices, well_preview_invoice_fetch) default to them when called without a period. Send it only for the user's month selection — never to bound a counterparty pick, which would overwrite that selection.
counterparties: the counterparties (vendors) the user selected, each { company_id, matched_connector_service_id }. Copy both ids off the row you listed them from; pass no display name. The selection belongs to the workspace this call is dispatched to, and a switch to another workspace clears it. One conversation holds one selection, so a new one replaces it; a selection sent for a workspace this conversation has switched away from is REFUSED instead, so a card the flow moved past cannot overwrite the pinned workspace's selection.
counterparty_periods: the months the counterparties card listed, sent alongside counterparties. The pick then narrows those months only, and a month it never covered is read in full. With none named, the months this conversation already holds bound the pick. This never becomes the conversation's selected months.
exempt_categories: the category keys the user marked as NOT burn on the exemption card, copied off what well_list_burn_exemptions returned. An EMPTY list is a real answer and records that they exempted nothing; omit the field entirely when they have not answered yet. The set belongs to the workspace this call is dispatched to, and a switch to another workspace clears it, but a change of months does not, because a category is or is not burn for the business whatever window is read next. One conversation holds one set, so a new one replaces it.
recurring_contexts: the billing context keys the user counts as recurring revenue on the recurring-contexts card, copied off what well_list_recurring_contexts returned. An EMPTY list is a real answer and records that they count nothing as recurring. It is scoped, cleared and replaced exactly like exempt_categories.
counted_account_types: the account types the user ticked as cash on the cash-scope card, copied off what well_list_cash_scope returned. An EMPTY list is a real answer and records that they count nothing as cash, which ends the run rather than reporting a zero total. It is scoped, cleared and replaced exactly like exempt_categories.
ack: "connectors", "bank", "categorize", "assign", "deploy", "invite" or "company_pick": records that the user answered that flow step, in the workspace this call is dispatched to. "company_pick" is the company candidates card's own ack: the card sends it on its Use click alongside the pin to the new company workspace, and on its Keep for later without moving the pin, so you do not send it yourself. "categorize", "deploy", "retarget", "company_pick" and "invite" also take ack_outcome: "done" when the user carried the step out, "keep_for_later" when they set it aside; both end the step. A switch to another workspace clears it, so the next workspace's card asks for its own click. An acknowledgement sent for a workspace this conversation has switched away from is REFUSED instead, so a card the flow moved past cannot un-confirm the step the pinned workspace's own card recorded.
next_step: the line the user picked on the next-steps card, as { skill, prompt } copied off that card's row. The prompt is the sentence the model reads as the user's own message, so it travels beside the slug rather than being rebuilt from it. The pick belongs to the workspace this call is dispatched to, and a switch to another workspace clears it.

Call it with NO argument at all to pin the workspace this call itself is dispatched to: its universal workspace_id, or the only workspace the token covers. workspace_ids is the PIN write and nothing else: it moves the pin AND replaces the workspace_queue, so a one-entry list ends a run that still had workspaces queued. Send it only to change the workspace. A call carrying periods, counterparties, exempt_categories, recurring_contexts, counted_account_types, ack or next_step needs no workspace_ids: its universal workspace_id targets that one call, and the pin and the queue stay where they are. Never re-pin the workspace this conversation already holds.

Every provided input is applied, and changed names the conversation fields this call wrote. pickup says what became of the write: "resumed" or "held_then_resumed" mean the model's own turn carries it on and the caller must send no reply of its own, "unwaited" or "exhausted" mean nothing is watching and the caller's reply is the only thing that moves the flow, and "stale" means the flow already answered this card, so the value is kept as a late edit and the caller says nothing. resumed is the boolean half of the first two. After a switch, every later call that omits workspace_id targets the pinned workspace, for reads and writes alike; passing workspace_id on a later call overrides it for that call only. well_list_workspaces reports the current conversation context, and well_wait_for_selection reads a card click back, instantly when it already landed here and after a short wait otherwise.

This changes nothing in the user's data.

Input Schema

TableJSON Schema

Name	Required	Description
`ack`	No	Acknowledge a flow step: "connectors" for the connect-tools step, "bank" for the bank step, "categorize" for the counterparty-categorization step, "assign" for the assign-owners step, "deploy" for the collect-agents step, "retarget" for the connector-retarget (data-migration) card, "company_pick" for the company-candidates card, "invite" for the invite-members card. "retarget" is the retarget card's own ack: the card sends it on its Confirm with ack_outcome "done", or on its Keep for later with "keep_for_later", so you do not send it yourself. The acknowledgement is scoped to the workspace this call is dispatched to, and a switch to another workspace clears it. An acknowledgement sent for a workspace this conversation has switched away from is refused, and the pinned workspace's own acknowledgement of that step stands.
`periods`	No	The months the user VALIDATED on the period card, stored as this conversation's selected_periods. Later period-scoped reads default to them when called without a period. This field is the user's month selection alone: to bound a counterparty pick, send counterparty_periods instead.
`next_step`	No	The next step the user picked on the well_propose_next_steps card, as the pair that card listed: the skill's slug and the sentence beside it. Both travel, because the sentence is what the model reads as the user's own message and the slug is what it loads. The pick is scoped to the workspace this call is dispatched to, and a switch to another workspace clears it.
`ack_outcome`	No	What the click said about the step: "done" when the user carried it out, "keep_for_later" when they set it aside on purpose. REQUIRED with ack "categorize" and "deploy" and "retarget" and "company_pick" and "invite", whose cards end on two buttons that mean different things, and refused with every other step, whose card confirms and nothing else.
`workspace_id`	No	Target 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.
`workspace_ids`	No	Ordered workspace selection, and the ONLY field that moves the pin: the FIRST entry becomes this conversation's pin, and the rest REPLACE the workspace_queue, so a one-entry list empties a queue that still holds workspaces. Every entry must be authorized for this connection, or the whole call is refused. Never send it to name the workspace of a periods, counterparties or ack call: the universal workspace_id already targets those, while a re-pin to the id this conversation already holds writes nothing and clears the queue.
`counterparties`	No	The counterparties the user selected, stored as this conversation's selected_counterparties and scoped to the workspace this call is dispatched to. At most 200, and a longer list is refused, so a select-all keeps to that bound. Copy the ids off the row: company_id, plus matched_connector_service_id when the row carries one. Send the card's months as counterparty_periods in the same call, so the pick applies to those months only; with none named, the months this conversation already holds bound it. The conversation holds ONE selection, so this REPLACES the previous one, but only when the call names the pinned workspace: a selection sent for a workspace this conversation has switched away from is refused, and the pinned workspace's selection stands.
`conversation_id`	No	The 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_key`	No	Optional client-supplied key. A retried write with the same key returns the original result instead of re-applying the operation.
`exempt_categories`	No	The categories the user marked as NOT burn, stored as this conversation's selected_exemptions and scoped to the workspace this call is dispatched to. Copy each category_key off the row well_list_burn_exemptions returned; never send a label. An EMPTY list is a real answer, since it records that the user exempted nothing, so send it when they clicked Continue with nothing ticked, and omit the field entirely when they have not answered. At most 100, the same bound well_sum_transactions accepts, so a recorded answer is always one the sum can run. The conversation holds ONE set, so this REPLACES the previous one; unlike a counterparty pick it survives a change of months, because a category is or is not burn for the business whatever window is read next.
`recurring_contexts`	No	The billing contexts the user counts as recurring revenue, stored as this conversation's selected_recurring_contexts and scoped to the workspace this call is dispatched to. Copy each context_key off the row well_list_recurring_contexts returned; never send a label. An EMPTY list is a real answer, since it records that the user counts nothing as recurring, so send it when they clicked Continue with nothing ticked, and omit the field entirely when they have not answered. At most 100, the same bound well_render_mrr accepts. The conversation holds ONE set, so this REPLACES the previous one, and like the exemptions it survives a change of months.
`counterparty_periods`	No	The months the counterparties card listed, which bound the pick sent as counterparties in the same call. Send it only with counterparties; it never becomes this conversation's selected months, so it cannot overwrite what the user validated on the period card. With none named, the months this conversation already holds bound the pick.
`counted_account_types`	No	The account types the user ticked as cash, stored as this conversation's selected_cash_scope and scoped to the workspace this call is dispatched to. Copy each account_type off the group well_list_cash_scope returned; never send a label. An EMPTY list is a real answer, since it records that the user counts nothing as cash, which ends the run rather than reporting a zero, so send it when they clicked Continue with nothing ticked, and omit the field entirely when they have not answered. The conversation holds ONE set, so this REPLACES the previous one, and like the exemptions it survives a change of months: a credit card is or is not cash for the business whatever window is read next.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No
`pickup`	Yes	What became of this write: "resumed" (a model wait took it), "held_then_resumed" (no wait yet, so the call was held until one consumed it), "unwaited" (nothing ever consumed it), "exhausted" (the model gave up on the card and ended the turn), "stale" (the flow already answered this card and moved past it — the value is recorded as a late edit). A card prefills a reply on "unwaited" and "exhausted" only.
`changed`	No	Which fields of this conversation's context this call wrote.
`resumed`	Yes	True when the model's own turn carries this write on — the derived half of `pickup` ("resumed" or "held_then_resumed"). A card that reads true must not prefill a reply; the conversation continues on its own.
`success`	Yes
`warning`	No	Present when this call opened a fresh lane because no conversation_id reached it: the write landed, and only a later call that passes the echoed conversation_id back can read it.
`acknowledged`	No
`workspace_id`	No
`workspace_name`	No
`conversation_id`	No	The conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
`workspace_queue`	No	The workspaces queued after the pinned one, in order.
`selected_periods`	No
`selected_next_step`	No	The next step this call recorded, echoed back as the card sent it.
`selected_cash_scope`	No
`selected_exemptions`	No
`acknowledged_outcome`	No	The answer the acknowledging click carried, echoed back on a step whose card offers two.
`conversation_id_note`	No	Present only when the server opened a fresh lane, stating that no choice recorded earlier was read.
`conversation_id_source`	No	Where the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.
`selected_counterparties`	No
`selected_recurring_contexts`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedSep 22, 2026

changedInput schema / properties / ack / description

Previous value: -"Acknowledge a flow step: \"connectors\" for the connect-tools step, \"bank\" for the bank step, \"categorize\" for the counterparty-categorization step, \"assign\" for the assign-owners step, \"deploy\" for the collect-agents step, \"retarget\" for the connector-retarget (data-migration) card, \"company_pick\" for the company-candidates card, \"invite\" for the invite-members card. \"retarget\" is the retarget card's own ack: the card sends it on its Confirm with ack_outcome \"done\", or on its Keep for later with \"keep_for_later\", so you do not send it yourself. The acknowledgement is scoped to the workspace this call is dispatched to, and a switch to another workspace clears it. An acknowledgement sent for a workspace this connection has switched away from is refused, and the pinned workspace's own acknowledgement of that step stands."New value: +"Acknowledge a flow step: \"connectors\" for the connect-tools step, \"bank\" for the bank step, \"categorize\" for the counterparty-categorization step, \"assign\" for the assign-owners step, \"deploy\" for the collect-agents step, \"retarget\" for the connector-retarget (data-migration) card, \"company_pick\" for the company-candidates card, \"invite\" for the invite-members card. \"retarget\" is the retarget card's own ack: the card sends it on its Confirm with ack_outcome \"done\", or on its Keep for later with \"keep_for_later\", so you do not send it yourself. The acknowledgement is scoped to the workspace this call is dispatched to, and a switch to another workspace clears it. An acknowledgement sent for a workspace this conversation has switched away from is refused, and the pinned workspace's own acknowledgement of that step stands."

addedInput schema / properties / conversation_id

Added value: +{
+  "description": "The 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.",
+  "type": "string"
+}

changedInput schema / properties / counted_account_types / description

Previous value: -"The account types the user ticked as cash, stored as this session's selected_cash_scope and scoped to the workspace this call is dispatched to. Copy each account_type off the group well_list_cash_scope returned; never send a label. An EMPTY list is a real answer — it records that the user counts nothing as cash, which ends the run rather than reporting a zero — so send it when they clicked Continue with nothing ticked, and omit the field entirely when they have not answered. The session holds ONE set, so this REPLACES the previous one, and like the exemptions it survives a change of months: a credit card is or is not cash for the business whatever window is read next."New value: +"The account types the user ticked as cash, stored as this conversation's selected_cash_scope and scoped to the workspace this call is dispatched to. Copy each account_type off the group well_list_cash_scope returned; never send a label. An EMPTY list is a real answer, since it records that the user counts nothing as cash, which ends the run rather than reporting a zero, so send it when they clicked Continue with nothing ticked, and omit the field entirely when they have not answered. The conversation holds ONE set, so this REPLACES the previous one, and like the exemptions it survives a change of months: a credit card is or is not cash for the business whatever window is read next."

changedInput schema / properties / counterparties / description

Previous value: -"The counterparties the user selected, stored as this session's selected_counterparties and scoped to the workspace this call is dispatched to. At most 200 — a longer list is refused, so a select-all keeps to that bound. Copy the ids off the row: company_id, plus matched_connector_service_id when the row carries one. Send the card's months as counterparty_periods in the same call, so the pick applies to those months only; with none named, the months this session already holds bound it. The session holds ONE selection, so this REPLACES the previous one — but only when the call names the pinned workspace: a selection sent for a workspace this connection has switched away from is refused, and the pinned workspace's selection stands."New value: +"The counterparties the user selected, stored as this conversation's selected_counterparties and scoped to the workspace this call is dispatched to. At most 200, and a longer list is refused, so a select-all keeps to that bound. Copy the ids off the row: company_id, plus matched_connector_service_id when the row carries one. Send the card's months as counterparty_periods in the same call, so the pick applies to those months only; with none named, the months this conversation already holds bound it. The conversation holds ONE selection, so this REPLACES the previous one, but only when the call names the pinned workspace: a selection sent for a workspace this conversation has switched away from is refused, and the pinned workspace's selection stands."

changedInput schema / properties / counterparty_periods / description

Previous value: -"The months the counterparties card listed, which bound the pick sent as counterparties in the same call. Send it only with counterparties; it never becomes this session's selected months, so it cannot overwrite what the user validated on the period card. With none named, the months this session already holds bound the pick."New value: +"The months the counterparties card listed, which bound the pick sent as counterparties in the same call. Send it only with counterparties; it never becomes this conversation's selected months, so it cannot overwrite what the user validated on the period card. With none named, the months this conversation already holds bound the pick."

changedInput schema / properties / exempt_categories / description

Previous value: -"The categories the user marked as NOT burn, stored as this session's selected_exemptions and scoped to the workspace this call is dispatched to. Copy each category_key off the row well_list_burn_exemptions returned; never send a label. An EMPTY list is a real answer — it records that the user exempted nothing — so send it when they clicked Continue with nothing ticked, and omit the field entirely when they have not answered. At most 100, the same bound well_sum_transactions accepts, so a recorded answer is always one the sum can run. The session holds ONE set, so this REPLACES the previous one; unlike a counterparty pick it survives a change of months, because a category is or is not burn for the business whatever window is read next."New value: +"The categories the user marked as NOT burn, stored as this conversation's selected_exemptions and scoped to the workspace this call is dispatched to. Copy each category_key off the row well_list_burn_exemptions returned; never send a label. An EMPTY list is a real answer, since it records that the user exempted nothing, so send it when they clicked Continue with nothing ticked, and omit the field entirely when they have not answered. At most 100, the same bound well_sum_transactions accepts, so a recorded answer is always one the sum can run. The conversation holds ONE set, so this REPLACES the previous one; unlike a counterparty pick it survives a change of months, because a category is or is not burn for the business whatever window is read next."

changedInput schema / properties / periods / description

Previous value: -"The months the user VALIDATED on the period card, stored as this session's selected_periods. Later period-scoped reads default to them when called without a period. This field is the user's month selection alone — to bound a counterparty pick, send counterparty_periods instead."New value: +"The months the user VALIDATED on the period card, stored as this conversation's selected_periods. Later period-scoped reads default to them when called without a period. This field is the user's month selection alone: to bound a counterparty pick, send counterparty_periods instead."

changedInput schema / properties / recurring_contexts / description

Previous value: -"The billing contexts the user counts as recurring revenue, stored as this session's selected_recurring_contexts and scoped to the workspace this call is dispatched to. Copy each context_key off the row well_list_recurring_contexts returned; never send a label. An EMPTY list is a real answer — it records that the user counts nothing as recurring — so send it when they clicked Continue with nothing ticked, and omit the field entirely when they have not answered. At most 100, the same bound well_render_mrr accepts. The session holds ONE set, so this REPLACES the previous one, and like the exemptions it survives a change of months."New value: +"The billing contexts the user counts as recurring revenue, stored as this conversation's selected_recurring_contexts and scoped to the workspace this call is dispatched to. Copy each context_key off the row well_list_recurring_contexts returned; never send a label. An EMPTY list is a real answer, since it records that the user counts nothing as recurring, so send it when they clicked Continue with nothing ticked, and omit the field entirely when they have not answered. At most 100, the same bound well_render_mrr accepts. The conversation holds ONE set, so this REPLACES the previous one, and like the exemptions it survives a change of months."

changedInput schema / properties / workspace_ids / description

Previous value: -"Ordered workspace selection, and the ONLY field that moves the pin: the FIRST entry becomes this connection's pin, and the rest REPLACE the workspace_queue — so a one-entry list empties a queue that still holds workspaces. Every entry must be authorized for this connection, or the whole call is refused. Never send it to name the workspace of a periods, counterparties or ack call: the universal workspace_id already targets those, while a re-pin to the id this connection already holds writes nothing and clears the queue."New value: +"Ordered workspace selection, and the ONLY field that moves the pin: the FIRST entry becomes this conversation's pin, and the rest REPLACE the workspace_queue, so a one-entry list empties a queue that still holds workspaces. Every entry must be authorized for this connection, or the whole call is refused. Never send it to name the workspace of a periods, counterparties or ack call: the universal workspace_id already targets those, while a re-pin to the id this conversation already holds writes nothing and clears the queue."

changedOutput schema / properties / changed / description

Previous value: -"Which session fields this call wrote."New value: +"Which fields of this conversation's context this call wrote."

addedOutput schema / properties / conversation_id

Added value: +{
+  "description": "The conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.",
+  "type": "string"
+}

addedOutput schema / properties / conversation_id_note

Added value: +{
+  "description": "Present only when the server opened a fresh lane, stating that no choice recorded earlier was read.",
+  "type": "string"
+}

addedOutput schema / properties / conversation_id_source

Added value: +{
+  "description": "Where the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.",
+  "enum": [
+    "host_meta",
+    "argument",
+    "minted"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / warning

Added value: +{
+  "description": "Present when this call opened a fresh lane because no conversation_id reached it: the write landed, and only a later call that passes the echoed conversation_id back can read it.",
+  "type": "string"
+}

Changed3 schema fields changedSep 21, 2026

addedInput schema / properties / counted_account_types

Added value: +{
+  "description": "The account types the user ticked as cash, stored as this session's selected_cash_scope and scoped to the workspace this call is dispatched to. Copy each account_type off the group well_list_cash_scope returned; never send a label. An EMPTY list is a real answer — it records that the user counts nothing as cash, which ends the run rather than reporting a zero — so send it when they clicked Continue with nothing ticked, and omit the field entirely when they have not answered. The session holds ONE set, so this REPLACES the previous one, and like the exemptions it survives a change of months: a credit card is or is not cash for the business whatever window is read next.",
+  "items": {
+    "enum": [
+      "deposit",
+      "credit",
+      "loan",
+      "investment",
+      "payroll",
+      "other"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

changedOutput schema / properties / changed / items / enum

Previous value: -[
-  "workspace",
-  "periods",
-  "counterparties",
-  "exemptions",
-  "recurring_contexts",
-  "next_step",
-  "connectors_ack",
-  "bank_ack",
-  "categorize_ack",
-  "assign_ack",
-  "deploy_ack",
-  "company_pick",
-  "accounting_settings_ack",
-  "retarget_ack",
-  "invite_ack"
-]New value: +[
+  "workspace",
+  "periods",
+  "counterparties",
+  "exemptions",
+  "recurring_contexts",
+  "cash_scope",
+  "next_step",
+  "connectors_ack",
+  "bank_ack",
+  "categorize_ack",
+  "assign_ack",
+  "deploy_ack",
+  "company_pick",
+  "accounting_settings_ack",
+  "retarget_ack",
+  "invite_ack"
+]

addedOutput schema / properties / selected_cash_scope

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed5 schema fields changedSep 16, 2026

changedInput schema / properties / ack / description

Previous value: -"Acknowledge a flow step: \"connectors\" for the connect-tools step, \"bank\" for the bank step, \"categorize\" for the counterparty-categorization step, \"assign\" for the assign-owners step, \"deploy\" for the collect-agents step, \"retarget\" for the connector-retarget (data-migration) card. \"retarget\" is the retarget card's own ack: the card sends it on its Confirm with ack_outcome \"done\", or on its Keep for later with \"keep_for_later\", so you do not send it yourself. The acknowledgement is scoped to the workspace this call is dispatched to, and a switch to another workspace clears it. An acknowledgement sent for a workspace this connection has switched away from is refused, and the pinned workspace's own acknowledgement of that step stands."New value: +"Acknowledge a flow step: \"connectors\" for the connect-tools step, \"bank\" for the bank step, \"categorize\" for the counterparty-categorization step, \"assign\" for the assign-owners step, \"deploy\" for the collect-agents step, \"retarget\" for the connector-retarget (data-migration) card, \"company_pick\" for the company-candidates card, \"invite\" for the invite-members card. \"retarget\" is the retarget card's own ack: the card sends it on its Confirm with ack_outcome \"done\", or on its Keep for later with \"keep_for_later\", so you do not send it yourself. The acknowledgement is scoped to the workspace this call is dispatched to, and a switch to another workspace clears it. An acknowledgement sent for a workspace this connection has switched away from is refused, and the pinned workspace's own acknowledgement of that step stands."

changedInput schema / properties / ack / enum

Previous value: -[
-  "connectors",
-  "bank",
-  "categorize",
-  "assign",
-  "deploy",
-  "company_pick",
-  "accounting_settings",
-  "retarget"
-]New value: +[
+  "connectors",
+  "bank",
+  "categorize",
+  "assign",
+  "deploy",
+  "company_pick",
+  "accounting_settings",
+  "retarget",
+  "invite"
+]

changedInput schema / properties / ack_outcome / description

Previous value: -"What the click said about the step: \"done\" when the user carried it out, \"keep_for_later\" when they set it aside on purpose. REQUIRED with ack \"categorize\" and \"deploy\" and \"retarget\", whose cards end on two buttons that mean different things, and refused with every other step, whose card confirms and nothing else."New value: +"What the click said about the step: \"done\" when the user carried it out, \"keep_for_later\" when they set it aside on purpose. REQUIRED with ack \"categorize\" and \"deploy\" and \"retarget\" and \"company_pick\" and \"invite\", whose cards end on two buttons that mean different things, and refused with every other step, whose card confirms and nothing else."

changedOutput schema / properties / acknowledged / enum

Previous value: -[
-  "connectors",
-  "bank",
-  "categorize",
-  "assign",
-  "deploy",
-  "company_pick",
-  "accounting_settings",
-  "retarget"
-]New value: +[
+  "connectors",
+  "bank",
+  "categorize",
+  "assign",
+  "deploy",
+  "company_pick",
+  "accounting_settings",
+  "retarget",
+  "invite"
+]

changedOutput schema / properties / changed / items / enum

Previous value: -[
-  "workspace",
-  "periods",
-  "counterparties",
-  "exemptions",
-  "recurring_contexts",
-  "next_step",
-  "connectors_ack",
-  "bank_ack",
-  "categorize_ack",
-  "assign_ack",
-  "deploy_ack",
-  "company_pick",
-  "accounting_settings_ack",
-  "retarget_ack"
-]New value: +[
+  "workspace",
+  "periods",
+  "counterparties",
+  "exemptions",
+  "recurring_contexts",
+  "next_step",
+  "connectors_ack",
+  "bank_ack",
+  "categorize_ack",
+  "assign_ack",
+  "deploy_ack",
+  "company_pick",
+  "accounting_settings_ack",
+  "retarget_ack",
+  "invite_ack"
+]

Changed7 schema fields changedSep 15, 2026

changedInput schema / properties / ack / description

Previous value: -"Acknowledge a flow step: \"connectors\" for the connect-tools step, \"bank\" for the bank step, \"categorize\" for the counterparty-categorization step, \"assign\" for the assign-owners step, \"deploy\" for the collect-agents step. The acknowledgement is scoped to the workspace this call is dispatched to, and a switch to another workspace clears it. An acknowledgement sent for a workspace this connection has switched away from is refused, and the pinned workspace's own acknowledgement of that step stands."New value: +"Acknowledge a flow step: \"connectors\" for the connect-tools step, \"bank\" for the bank step, \"categorize\" for the counterparty-categorization step, \"assign\" for the assign-owners step, \"deploy\" for the collect-agents step, \"retarget\" for the connector-retarget (data-migration) card. \"retarget\" is the retarget card's own ack: the card sends it on its Confirm with ack_outcome \"done\", or on its Keep for later with \"keep_for_later\", so you do not send it yourself. The acknowledgement is scoped to the workspace this call is dispatched to, and a switch to another workspace clears it. An acknowledgement sent for a workspace this connection has switched away from is refused, and the pinned workspace's own acknowledgement of that step stands."

changedInput schema / properties / ack / enum

Previous value: -[
-  "connectors",
-  "bank",
-  "categorize",
-  "assign",
-  "deploy"
-]New value: +[
+  "connectors",
+  "bank",
+  "categorize",
+  "assign",
+  "deploy",
+  "company_pick",
+  "accounting_settings",
+  "retarget"
+]

changedInput schema / properties / ack_outcome / description

Previous value: -"What the click said about the step: \"done\" when the user carried it out, \"keep_for_later\" when they set it aside on purpose. REQUIRED with ack \"categorize\" and \"deploy\", whose cards end on two buttons that mean different things, and refused with every other step, whose card confirms and nothing else."New value: +"What the click said about the step: \"done\" when the user carried it out, \"keep_for_later\" when they set it aside on purpose. REQUIRED with ack \"categorize\" and \"deploy\" and \"retarget\", whose cards end on two buttons that mean different things, and refused with every other step, whose card confirms and nothing else."

addedInput schema / properties / recurring_contexts

Added value: +{
+  "description": "The billing contexts the user counts as recurring revenue, stored as this session's selected_recurring_contexts and scoped to the workspace this call is dispatched to. Copy each context_key off the row well_list_recurring_contexts returned; never send a label. An EMPTY list is a real answer — it records that the user counts nothing as recurring — so send it when they clicked Continue with nothing ticked, and omit the field entirely when they have not answered. At most 100, the same bound well_render_mrr accepts. The session holds ONE set, so this REPLACES the previous one, and like the exemptions it survives a change of months.",
+  "items": {
+    "maxLength": 200,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 100,
+  "type": "array"
+}

changedOutput schema / properties / acknowledged / enum

Previous value: -[
-  "connectors",
-  "bank",
-  "categorize",
-  "assign",
-  "deploy"
-]New value: +[
+  "connectors",
+  "bank",
+  "categorize",
+  "assign",
+  "deploy",
+  "company_pick",
+  "accounting_settings",
+  "retarget"
+]

changedOutput schema / properties / changed / items / enum

Previous value: -[
-  "workspace",
-  "periods",
-  "counterparties",
-  "exemptions",
-  "connectors_ack",
-  "bank_ack",
-  "categorize_ack",
-  "assign_ack",
-  "deploy_ack",
-  "next_step"
-]New value: +[
+  "workspace",
+  "periods",
+  "counterparties",
+  "exemptions",
+  "recurring_contexts",
+  "next_step",
+  "connectors_ack",
+  "bank_ack",
+  "categorize_ack",
+  "assign_ack",
+  "deploy_ack",
+  "company_pick",
+  "accounting_settings_ack",
+  "retarget_ack"
+]

addedOutput schema / properties / selected_recurring_contexts

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed3 schema fields changedSep 11, 2026

addedInput schema / properties / next_step

Added value: +{
+  "additionalProperties": false,
+  "description": "The next step the user picked on the well_propose_next_steps card, as the pair that card listed: the skill's slug and the sentence beside it. Both travel, because the sentence is what the model reads as the user's own message and the slug is what it loads. The pick is scoped to the workspace this call is dispatched to, and a switch to another workspace clears it.",
+  "properties": {
+    "prompt": {
+      "description": "The sentence the card listed beside the skill, copied as written.",
+      "maxLength": 160,
+      "minLength": 1,
+      "type": "string"
+    },
+    "skill": {
+      "description": "The slug of the skill the picked line offers, exactly as the card listed it.",
+      "pattern": "^[a-z0-9-]{1,64}$",
+      "type": "string"
+    }
+  },
+  "required": [
+    "skill",
+    "prompt"
+  ],
+  "type": "object"
+}

changedOutput schema / properties / changed / items / enum

Previous value: -[
-  "workspace",
-  "periods",
-  "counterparties",
-  "exemptions",
-  "connectors_ack",
-  "bank_ack",
-  "categorize_ack",
-  "assign_ack",
-  "deploy_ack"
-]New value: +[
+  "workspace",
+  "periods",
+  "counterparties",
+  "exemptions",
+  "connectors_ack",
+  "bank_ack",
+  "categorize_ack",
+  "assign_ack",
+  "deploy_ack",
+  "next_step"
+]

addedOutput schema / properties / selected_next_step

Added value: +{
+  "additionalProperties": false,
+  "description": "The next step this call recorded, echoed back as the card sent it.",
+  "properties": {
+    "prompt": {
+      "description": "The sentence the card listed beside the skill, copied as written.",
+      "maxLength": 160,
+      "minLength": 1,
+      "type": "string"
+    },
+    "skill": {
+      "description": "The slug of the skill the picked line offers, exactly as the card listed it.",
+      "pattern": "^[a-z0-9-]{1,64}$",
+      "type": "string"
+    }
+  },
+  "required": [
+    "skill",
+    "prompt"
+  ],
+  "type": "object"
+}

Changed9 schema fields changedSep 10, 2026

changedInput schema / properties / ack / description

Previous value: -"Acknowledge a flow step: \"connectors\" for the connect-tools step, \"bank\" for the bank step. The acknowledgement is scoped to the workspace this call is dispatched to, and a switch to another workspace clears it. An acknowledgement sent for a workspace this connection has switched away from is refused, and the pinned workspace's own acknowledgement of that step stands."New value: +"Acknowledge a flow step: \"connectors\" for the connect-tools step, \"bank\" for the bank step, \"categorize\" for the counterparty-categorization step, \"assign\" for the assign-owners step, \"deploy\" for the collect-agents step. The acknowledgement is scoped to the workspace this call is dispatched to, and a switch to another workspace clears it. An acknowledgement sent for a workspace this connection has switched away from is refused, and the pinned workspace's own acknowledgement of that step stands."

changedInput schema / properties / ack / enum

Previous value: -[
-  "connectors",
-  "bank"
-]New value: +[
+  "connectors",
+  "bank",
+  "categorize",
+  "assign",
+  "deploy"
+]

addedInput schema / properties / ack_outcome

Added value: +{
+  "description": "What the click said about the step: \"done\" when the user carried it out, \"keep_for_later\" when they set it aside on purpose. REQUIRED with ack \"categorize\" and \"deploy\", whose cards end on two buttons that mean different things, and refused with every other step, whose card confirms and nothing else.",
+  "enum": [
+    "done",
+    "keep_for_later"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / acknowledged / enum

Previous value: -[
-  "connectors",
-  "bank"
-]New value: +[
+  "connectors",
+  "bank",
+  "categorize",
+  "assign",
+  "deploy"
+]

addedOutput schema / properties / acknowledged_outcome

Added value: +{
+  "description": "The answer the acknowledging click carried, echoed back on a step whose card offers two.",
+  "enum": [
+    "done",
+    "keep_for_later"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / changed / items / enum

Previous value: -[
-  "workspace",
-  "periods",
-  "counterparties",
-  "exemptions",
-  "connectors_ack",
-  "bank_ack"
-]New value: +[
+  "workspace",
+  "periods",
+  "counterparties",
+  "exemptions",
+  "connectors_ack",
+  "bank_ack",
+  "categorize_ack",
+  "assign_ack",
+  "deploy_ack"
+]

addedOutput schema / properties / pickup

Added value: +{
+  "description": "What became of this write: \"resumed\" (a model wait took it), \"held_then_resumed\" (no wait yet, so the call was held until one consumed it), \"unwaited\" (nothing ever consumed it), \"exhausted\" (the model gave up on the card and ended the turn), \"stale\" (the flow already answered this card and moved past it — the value is recorded as a late edit). A card prefills a reply on \"unwaited\" and \"exhausted\" only.",
+  "enum": [
+    "resumed",
+    "held_then_resumed",
+    "unwaited",
+    "exhausted",
+    "stale"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / resumed

Added value: +{
+  "description": "True when the model's own turn carries this write on — the derived half of `pickup` (\"resumed\" or \"held_then_resumed\"). A card that reads true must not prefill a reply; the conversation continues on its own.",
+  "type": "boolean"
+}

changedOutput schema / required

Previous value: -[
-  "success"
-]New value: +[
+  "success",
+  "resumed",
+  "pickup"
+]

Changed3 schema fields changedSep 7, 2026

addedInput schema / properties / exempt_categories

Added value: +{
+  "description": "The categories the user marked as NOT burn, stored as this session's selected_exemptions and scoped to the workspace this call is dispatched to. Copy each category_key off the row well_list_burn_exemptions returned; never send a label. An EMPTY list is a real answer — it records that the user exempted nothing — so send it when they clicked Continue with nothing ticked, and omit the field entirely when they have not answered. At most 100, the same bound well_sum_transactions accepts, so a recorded answer is always one the sum can run. The session holds ONE set, so this REPLACES the previous one; unlike a counterparty pick it survives a change of months, because a category is or is not burn for the business whatever window is read next.",
+  "items": {
+    "maxLength": 200,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 100,
+  "type": "array"
+}

changedOutput schema / properties / changed / items / enum

Previous value: -[
-  "workspace",
-  "periods",
-  "counterparties",
-  "connectors_ack",
-  "bank_ack"
-]New value: +[
+  "workspace",
+  "periods",
+  "counterparties",
+  "exemptions",
+  "connectors_ack",
+  "bank_ack"
+]

addedOutput schema / properties / selected_exemptions

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed1 schema field changedAug 31, 2026

changedInput schema / properties / workspace_id / description

Previous value: -"Target workspace. Omit to use the only authorized workspace, or (for read tools) to query all authorized workspaces grouped by workspace. Required for write tools when the token authorizes more than one workspace."New value: +"Target 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."

Changed7 schema fields changedAug 26, 2026

changedInput schema / properties / ack / description

Previous value: -"Acknowledge a flow step: \"connectors\" for the connect-tools step, \"bank\" for the bank step."New value: +"Acknowledge a flow step: \"connectors\" for the connect-tools step, \"bank\" for the bank step. The acknowledgement is scoped to the workspace this call is dispatched to, and a switch to another workspace clears it. An acknowledgement sent for a workspace this connection has switched away from is refused, and the pinned workspace's own acknowledgement of that step stands."

addedInput schema / properties / counterparties

Added value: +{
+  "description": "The counterparties the user selected, stored as this session's selected_counterparties and scoped to the workspace this call is dispatched to. At most 200 — a longer list is refused, so a select-all keeps to that bound. Copy the ids off the row: company_id, plus matched_connector_service_id when the row carries one. Send the card's months as counterparty_periods in the same call, so the pick applies to those months only; with none named, the months this session already holds bound it. The session holds ONE selection, so this REPLACES the previous one — but only when the call names the pinned workspace: a selection sent for a workspace this connection has switched away from is refused, and the pinned workspace's selection stands.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "company_id": {
+        "description": "The counterparty company's id, as listed by well_list_counterparties or well_list_missing_invoices.",
+        "format": "uuid",
+        "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+        "type": "string"
+      },
+      "matched_connector_service_id": {
+        "anyOf": [
+          {
+            "minLength": 1,
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "The matched provider's connector service id, copied from the row's matched_connector_service_id. Omit or pass null when the row matched no provider; never substitute the provider's name."
+      }
+    },
+    "required": [
+      "company_id"
+    ],
+    "type": "object"
+  },
+  "maxItems": 200,
+  "minItems": 1,
+  "type": "array"
+}

addedInput schema / properties / counterparty_periods

Added value: +{
+  "description": "The months the counterparties card listed, which bound the pick sent as counterparties in the same call. Send it only with counterparties; it never becomes this session's selected months, so it cannot overwrite what the user validated on the period card. With none named, the months this session already holds bound the pick.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "calendar_month": {
+        "description": "Calendar month, 1 = January … 12 = December.",
+        "maximum": 12,
+        "minimum": 1,
+        "type": "integer"
+      },
+      "calendar_year": {
+        "description": "Calendar year, e.g. 2026.",
+        "maximum": 2100,
+        "minimum": 2000,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "calendar_year",
+      "calendar_month"
+    ],
+    "type": "object"
+  },
+  "maxItems": 12,
+  "minItems": 1,
+  "type": "array"
+}

changedInput schema / properties / periods / description

Previous value: -"The months the user selected, stored as this session's selected_periods. Later period-scoped reads default to them when called without a period."New value: +"The months the user VALIDATED on the period card, stored as this session's selected_periods. Later period-scoped reads default to them when called without a period. This field is the user's month selection alone — to bound a counterparty pick, send counterparty_periods instead."

changedInput schema / properties / workspace_ids / description

Previous value: -"Ordered workspace selection: the FIRST entry becomes this connection's pin, the rest the workspace_queue to work through afterwards. Every entry must be authorized for this connection, or the whole call is refused."New value: +"Ordered workspace selection, and the ONLY field that moves the pin: the FIRST entry becomes this connection's pin, and the rest REPLACE the workspace_queue — so a one-entry list empties a queue that still holds workspaces. Every entry must be authorized for this connection, or the whole call is refused. Never send it to name the workspace of a periods, counterparties or ack call: the universal workspace_id already targets those, while a re-pin to the id this connection already holds writes nothing and clears the queue."

changedOutput schema / properties / changed / items / enum

Previous value: -[
-  "workspace",
-  "periods",
-  "connectors_ack",
-  "bank_ack"
-]New value: +[
+  "workspace",
+  "periods",
+  "counterparties",
+  "connectors_ack",
+  "bank_ack"
+]

addedOutput schema / properties / selected_counterparties

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "company_id": {
+        "description": "The counterparty company's id, as listed by well_list_counterparties or well_list_missing_invoices.",
+        "format": "uuid",
+        "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+        "type": "string"
+      },
+      "matched_connector_service_id": {
+        "anyOf": [
+          {
+            "minLength": 1,
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "The matched provider's connector service id, copied from the row's matched_connector_service_id. Omit or pass null when the row matched no provider; never substitute the provider's name."
+      }
+    },
+    "required": [
+      "company_id"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

AddedAug 21, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations only indicate readOnlyHint=false and destructiveHint=false, so the description carries the behavioral burden and handles it thoroughly. It discloses that writes are refused for workspaces switched away from, that empty lists are meaningful answers, that scope is cleared on workspace switch but survives month changes, and that 'This changes nothing in the user's data.' It also explains the pickup return states and whether the caller must reply. No contradiction with annotations.

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

Conciseness4/5

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

The description is front-loaded with the core purpose and then per-field semantics, which is appropriate for a tool with 13 parameters and complex scoping rules. It is long and somewhat repetitive with the input schema, restating empty-list and scoping rules for three nearly identical fields, but each sentence does add operational guidance. It could be tightened without losing value, but it is not padded.

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 highly complex, stateful tool with 13 parameters and no required parameters, the description covers all key dimensions: what each field stores, scoping and clearing rules, refusal behavior, the meaning of return fields (changed, pickup, resumed), and the effect of a switch on subsequent calls. It even explains when the caller should not reply. Nothing an agent needs to invoke this correctly is missing.

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

Parameters5/5

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

Schema coverage is 100%, so the baseline is 3, but the description goes far beyond the schema: it explains that the first workspace_ids entry becomes the pin and the rest replace the queue, that a one-entry list empties the queue, that empty lists for exempt_categories/recurring_contexts/counted_account_types are real answers, that counterparty_periods never becomes the selected months, and that stale acks are refused. These are essential semantic distinctions the schema alone does not convey.

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?

The first sentence states a specific verb and resource: 'Write this conversation's context — the one place its standing choices live.' It goes on to enumerate exactly what is recorded (workspace pin/queue, months, counterparties, step acknowledgements) and explicitly frames this as the tool widget cards call. This clearly differentiates it from the other well_* tools, which either read context or perform domain operations.

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?

The description gives explicit when-to-use and when-not-to-use guidance: 'Call it with NO argument at all to pin the workspace', 'Send it only to change the workspace', 'Never re-pin the workspace this conversation already holds', and it explains that scoped writes such as periods or ack require no workspace_ids. It also references the related tools well_list_workspaces and well_wait_for_selection to route the agent correctly.

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

All Well tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?