EAD Factory MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

notification_receiver_add

Instructions

Adds one or more receivers to a draft notification request — each receiver becomes its own per-channel notification under the shared requestId (there is no separate receiverId; track receivers by the notificationIds this call returns). Use once per batch of receivers before calling notification_request_send. Requires: notification_request_create → requestId. Each receiver's shape depends on its provider (SMTP/SMS/NOTICEMAN/WFB) — see the schema for the fields each variant needs. Notification delivery provider: SMTP = Email delivery. | SMS = SMS text message delivery. | NOTICEMAN = EAD Factory's own certified notification channel (qualified electronic delivery). | NOTICEMAN_AND_WHATSAPP = Certified channel plus a WhatsApp copy. | NOTICEMAN_AND_WHATSAPP_AND_RCS = Certified channel plus WhatsApp and RCS copies. | NOTICEMAN_AND_RCS = Certified channel plus an RCS (Rich Communication Services) copy. | WFB = WhatsApp Business messaging, uncertified (no Noticeman qualified channel). | RCS = RCS (Rich Communication Services) messaging only, uncertified.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`receivers`	Yes
`requestId`	Yes	UUID of the notification request. Obtain from notification_request_create.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`requestId`	No
`notificationIds`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.4.0Sep 14, 2026

changedInput schema / properties / receivers / items / oneOf

Previous value: -[
-  {
-    "properties": {
-      "address": {
-        "format": "email",
-        "minLength": 1,
-        "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
-        "type": "string"
-      },
-      "metadata": {
-        "additionalProperties": {
-          "type": "string"
-        },
-        "propertyNames": {
-          "type": "string"
-        },
-        "type": "object"
-      },
-      "name": {
-        "type": "string"
-      },
-      "provider": {
-        "const": "Notification_AddReceiverEmailNotificationRequestModel",
-        "type": "string"
-      }
-    },
-    "required": [
-      "provider",
-      "address"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "address": {
-        "format": "email",
-        "minLength": 1,
-        "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
-        "type": "string"
-      },
-      "metadata": {
-        "additionalProperties": {
-          "type": "string"
-        },
-        "propertyNames": {
-          "type": "string"
-        },
-        "type": "object"
-      },
-      "name": {
-        "type": "string"
-      },
-      "phone": {
-        "type": "string"
-      },
-      "provider": {
-        "const": "Notification_AddReceiverNoticemanNotificationRequestModel",
-        "type": "string"
-      },
-      "type": {
-        "enum": [
-          "TO",
-          "CC",
-          "BCC"
-        ],
-        "type": "string"
-      }
-    },
-    "required": [
-      "provider",
-      "type",
-      "address"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "address": {
-        "minLength": 1,
-        "type": "string"
-      },
-      "provider": {
-        "const": "Notification_AddReceiverSmsNotificationRequestModel",
-        "type": "string"
-      }
-    },
-    "required": [
-      "provider",
-      "address"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "address": {
-        "minLength": 1,
-        "type": "string"
-      },
-      "provider": {
-        "const": "Notification_AddReceiverWfbNotificationRequestModel",
-        "type": "string"
-      }
-    },
-    "required": [
-      "provider",
-      "address"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "properties": {
+      "address": {
+        "format": "email",
+        "minLength": 1,
+        "pattern": "^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
+        "type": "string"
+      },
+      "metadata": {
+        "additionalProperties": {
+          "type": "string"
+        },
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "name": {
+        "type": "string"
+      },
+      "provider": {
+        "const": "Notification_AddReceiverEmailNotificationRequestModel",
+        "type": "string"
+      }
+    },
+    "required": [
+      "provider",
+      "address"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "address": {
+        "format": "email",
+        "minLength": 1,
+        "pattern": "^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
+        "type": "string"
+      },
+      "metadata": {
+        "additionalProperties": {
+          "type": "string"
+        },
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "name": {
+        "type": "string"
+      },
+      "phone": {
+        "type": "string"
+      },
+      "provider": {
+        "const": "Notification_AddReceiverNoticemanNotificationRequestModel",
+        "type": "string"
+      },
+      "type": {
+        "enum": [
+          "TO",
+          "CC",
+          "BCC"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "provider",
+      "type",
+      "address"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "address": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "provider": {
+        "const": "Notification_AddReceiverSmsNotificationRequestModel",
+        "type": "string"
+      }
+    },
+    "required": [
+      "provider",
+      "address"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "address": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "provider": {
+        "const": "Notification_AddReceiverWfbNotificationRequestModel",
+        "type": "string"
+      }
+    },
+    "required": [
+      "provider",
+      "address"
+    ],
+    "type": "object"
+  }
+]

First observedv1.3.1Aug 5, 2026

TDQS

A3.7/5.0

Behavior4/5

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

The description discloses meaningful behavioral traits beyond the minimal annotations: there is no separate receiverId, receivers must be tracked by the notificationIds returned, and each receiver becomes its own per-channel notification. This adds real operational context that annotations do not provide, and there is no contradiction.

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

Conciseness2/5

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

The core workflow guidance is front-loaded and useful, but the description becomes verbose with a long provider enumeration that is partially redundant with the schema and partially contradictory. The extra provider variants not present in the schema make the description longer without adding correct value.

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

Completeness3/5

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

The description covers the workflow, batching, and return tracking semantics, and the schema itself documents the receiver variants in detail. However, it is incomplete regarding the actual provider const values expected by the schema, and it introduces confusion by listing invalid provider options. Overall adequate but with a significant gap.

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

Parameters2/5

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

The description adds some meaning by defining provider types like SMTP, SMS, NOTICEMAN, and WFB, but it also lists providers such as NOTICEMAN_AND_WHATSAPP and RCS that do not appear anywhere in the schema's oneOf consts. It also fails to map the human-readable provider names to the actual schema const values like Notification_AddReceiverEmailNotificationRequestModel, which can mislead an agent into constructing invalid requests.

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 description states a specific action and object: 'Adds one or more receivers to a draft notification request.' It also clarifies the unique behavior that each receiver becomes its own per-channel notification under a shared requestId, which clearly distinguishes it from sibling tools like notification_request_create and notification_request_send.

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?

The description gives explicit sequencing: it requires notification_request_create → requestId and instructs to use once per batch before calling notification_request_send. It does not explicitly list when-not-to-use alternatives, but the workflow context is clear enough for an agent to select it appropriately.

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

Deploy Server