Well

Send notification

well_send_notification

Send a notification to the user (the caller only, never another person), on the channel they prefer: WhatsApp or email.

Use it when the user asks to be notified or reminded, or when a skill tells you to notify them. It is not a way to answer in this conversation: answer in the chat as usual.

kind: the notification kind. The kinds and the params each one takes:
well_notification: A general notification to the user: a short headline and a plain-language message. Params: {"title":{"type":"string","minLength":1,"maxLength":120,"description":"Short headline of the notification, used as the email subject."},"message":{"type":"string","minLength":1,"maxLength":2000,"description":"The notification text, in plain language, addressed to the user."}}. Required: title, message.
params: the params of that kind, as an object.
channel: leave it out so the user's own preference decides. Pass it only when the user names a channel for this one notification.

The result names the channel the notification really went out on. When it differs from the one the user asked for, the notification went by email instead: say so. The call is refused, with the reason, when the params are invalid or the kind has no template for the channel; never retry with other values on your own.

Input Schema

Name	Required	Description
`kind`	Yes	The notification kind to send (see the kinds listed in this tool's description).
`params`	Yes	The params of the chosen kind, as an object with the fields the kind lists.
`channel`	No	Send on this channel for this one notification. Leave out to use the user's preference.
`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.
`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.
`workspace_scope`	No	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.

Output Schema

Name	Required	Description
`code`	No
`kind`	No	The notification kind that was sent.
`error`	No
`channel`	No	The channel the notification went out on, which is email after a fallback.
`success`	Yes
`reply_lines`	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.
`near_candidates`	No
`newly_connected`	No	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.
`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.
`near_candidates_truncated`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 28, 2026

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"
+}
```

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"
+}

Changed1 schema field changedOct 12, 2026

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."

Changed1 schema field changedOct 8, 2026

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"
+}

AddedOct 6, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Annotations only declare the write/safety profile; the description adds the behaviors that matter: a silent channel fallback to email that the agent must disclose, a refusal path with reason for invalid params or missing channel template, and an explicit 'never retry with other values on your own' instruction. It also states that the response reports the channel actually used. That is real disclosure beyond what annotations and schema provide.

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 purpose, then when-to-use, then when-not, then mechanics — the ordering an agent needs. The inline JSON schema fragment for `well_notification` is verbose but load-bearing, since the schema leaves `params` open. Slightly long overall, but no sentence is padding.

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?

For a 7-parameter write tool with nested objects, three enums and an output schema, the description covers the decision-critical parts: kind selection, param shape, channel default, fallback disclosure, and failure handling. Return values need not be explained because an output schema exists. Workspace and conversation plumbing is left entirely to the schema, which is documented at full coverage.

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 the baseline is 3, but the description earns more: `params` is an open object (additionalProperties: {}) and the schema for `kind` explicitly defers to the description, which spells out the `well_notification` payload fields, their limits, and required keys. It also explains the channel-omission default. It does not touch workspace_id/conversation_id/idempotency_key, which the schema already documents.

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

Purpose4/5

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

States a specific verb and resource with tight scope: 'Send a notification to the user (the caller only, never another person), on the channel they prefer: WhatsApp or email.' An agent immediately knows what happens and to whom. It stops short of naming the sibling it is not (e.g. well_send_message, well_send_email_draft), so the differentiation comes from the exclusion 'never another person' rather than explicit routing.

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 a clear positive trigger ('when the user asks to be notified or reminded, or when a skill tells you to notify them') and a clear negative one ('It is not a way to answer in this conversation: answer in the chat as usual'). That is genuine when/when-not guidance. No alternative tool is named for the other-person or chat cases, which keeps it from a 5.

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?