Skip to main content
Glama

Set communication preference

well_set_communication_preference

Set the channel Well uses to notify the user (the caller only, never another member).

  • channel: where notifications go: "whatsapp", "email", or "slack" (a direct message from Well in the user's own Slack; only for schedule_run_report).

  • kind: one notification kind (see well_list_communication_kinds), or schedule_run_report for the reports of the user's routines, the morning brief included. Omit it to set the default for every notification; a kind's own preference wins over that default.

The call is refused, with the reason, when the kind has no template for the channel (the refusal lists the supported channels) or when the user cannot receive on that channel now, e.g. WhatsApp is not linked. Tell the user the reason; never retry with another channel on your own.

Input Schema

NameRequiredDescriptionDefault
kindNoThe notification kind this preference applies to. Omit it to set the default for every notification.
channelYesThe channel to send these notifications on.
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
codeNo
kindNoThe kind the preference applies to, or null for every notification.
errorNo
channelNo
successYes
reply_linesNo
conversation_idNoThe conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
near_candidatesNo
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.
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.
near_candidates_truncatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • changedInput schema / properties / channel / enum
      Previous value: -[
      -  "email",
      -  "whatsapp",
      -  "outbound-email"
      -]New value: +[
      +  "email",
      +  "whatsapp",
      +  "outbound-email",
      +  "slack"
      +]
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "well_notification"
      -]New value: +[
      +  "well_notification",
      +  "schedule_run_report"
      +]
    • changedOutput schema / properties / channel / enum
      Previous value: -[
      -  "email",
      -  "whatsapp",
      -  "outbound-email"
      -]New value: +[
      +  "email",
      +  "whatsapp",
      +  "outbound-email",
      +  "slack"
      +]
    • addedOutput schema / properties / code
      Added value: +{
      +  "type": "string"
      +}
    • removedOutput schema / properties / kind / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / kind / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • addedOutput schema / properties / near_candidates
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "company_id": {
      +        "type": "string"
      +      },
      +      "name": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "company_id",
      +      "name"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / near_candidates_truncated
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / reply_lines
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  2. 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."
  3. 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"
      +}
  4. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (readOnly=false, destructive=false, openWorld=false) it discloses refusal conditions (no template for channel, channel not currently linked), that the refusal carries a reason and lists supported channels, and an explicit no-auto-retry policy with a user-facing instruction. This is precisely the operational context annotations can't convey.

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?

Front-loaded with a one-line purpose, then bulleted parameter semantics, then a refusal section. Efficient, though it restates the channel enum values already in the schema and could trim that duplication.

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

Completeness4/5

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

Covers the mutation's failure modes, precedence rules, and user-facing follow-up; return values needn't be explained since an output schema exists. The one gap is the unmentioned 'outbound-email' enum value, an agent may not know how it differs from 'email'.

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?

Adds real semantics over a 100%-covered schema: `kind` omission means a global default and a per-kind setting wins over it; `channel` slack is limited to schedule_run_report. However it lists only three channels while the schema enum contains a fourth ('outbound-email'), leaving that value unexplained.

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?

States a specific verb+resource ('Set the channel Well uses to notify the user') with an explicit scope qualifier (the caller only, never another member), which cleanly separates it from siblings like well_send_notification and well_upsert_preference.

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

Usage Guidelines4/5

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

Gives clear when-to-use rules: omit `kind` to set the default, per-kind preference overrides the default, and points to well_list_communication_kinds for valid kinds. It doesn't explicitly contrast with well_upsert_preference or well_send_notification, so an agent must infer those boundaries.

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