EAD Factory MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

notification_request_create

Instructions

Creates a new notification request (draft) — the top-level container for receivers and attachments in a certified-notification flow. Use this first, before any other Notification-manager tool. No prerequisites. Set autosend: true to also send immediately on activation of the first receiver batch, or leave it false to add receivers/documents over several calls before calling notification_request_send yourself. Returns requestId and one notificationId per receiver already on the request (if any were included inline).

Input Schema

TableJSON Schema

Name	Required	Description
`data`	No
`content`	No
`autosend`	No
`language`	Yes
`metadata`	No
`requestId`	No	OPTIONAL. Supply a UUID here only if you want to choose the new request's id yourself; omit it and the API assigns one. Either way this call RETURNS the requestId that every other Notification tool then requires — do not try to obtain it beforehand.

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedv1.4.0Sep 14, 2026

removedInput schema / properties / data / properties / noticeman / allOf

Removed value: -[
-  {
-    "properties": {
-      "attachments": {
-        "items": {
-          "properties": {
-            "fileSize": {
-              "maximum": 9007199254740991,
-              "minimum": 1,
-              "type": "integer"
-            },
-            "filename": {
-              "minLength": 1,
-              "type": "string"
-            },
-            "hash": {
-              "minLength": 1,
-              "type": "string"
-            }
-          },
-          "required": [
-            "filename",
-            "hash"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "externalAttachments": {
-        "items": {
-          "properties": {
-            "filename": {
-              "minLength": 1,
-              "type": "string"
-            },
-            "hash": {
-              "type": "string"
-            },
-            "id": {
-              "minLength": 1,
-              "type": "string"
-            },
-            "type": {
-              "minLength": 1,
-              "pattern": "EVIDENCE|REPORT|REPORT_PACKAGE",
-              "type": "string"
-            }
-          },
-          "required": [
-            "id",
-            "type",
-            "filename"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "parameters": {
-        "additionalProperties": {
-          "type": "string"
-        },
-        "propertyNames": {
-          "type": "string"
-        },
-        "type": "object"
-      },
-      "receiver": {
-        "items": {
-          "allOf": [
-            {
-              "properties": {
-                "address": {
-                  "format": "email",
-                  "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
-                  "type": "string"
-                },
-                "addressReplyTo": {
-                  "format": "email",
-                  "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
-                  "type": "string"
-                },
-                "name": {
-                  "type": "string"
-                }
-              },
-              "type": "object"
-            },
-            {
-              "properties": {
-                "metadata": {
-                  "additionalProperties": {
-                    "type": "string"
-                  },
-                  "propertyNames": {
-                    "type": "string"
-                  },
-                  "type": "object"
-                },
-                "phone": {
-                  "type": "string"
-                },
-                "type": {
-                  "enum": [
-                    "TO",
-                    "CC",
-                    "BCC"
-                  ],
-                  "type": "string"
-                }
-              },
-              "type": "object"
-            }
-          ]
-        },
-        "minItems": 1,
-        "type": "array"
-      },
-      "sender": {
-        "properties": {
-          "address": {
-            "format": "email",
-            "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
-            "type": "string"
-          },
-          "addressReplyTo": {
-            "format": "email",
-            "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
-            "type": "string"
-          },
-          "name": {
-            "type": "string"
-          }
-        },
-        "type": "object"
-      },
-      "subject": {
-        "minLength": 1,
-        "type": "string"
-      },
-      "template": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "receiver",
-      "subject"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "limitResponse": {
-        "maximum": 720,
-        "minimum": 0,
-        "type": "integer"
-      },
-      "notificationType": {
-        "enum": [
-          "ACCEPTED_OR_NOT",
-          "RECEIVED_AGREE",
-          "LONG_RESPONSE",
-          "NO_RESPONSE"
-        ],
-        "type": "string"
-      },
-      "reminder": {
-        "maximum": 720,
-        "minimum": 24,
-        "type": "integer"
-      },
-      "scheduledAt": {
-        "format": "date-time",
-        "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$",
-        "type": "string"
-      }
-    },
-    "required": [
-      "notificationType"
-    ],
-    "type": "object"
-  }
-]

addedInput schema / properties / data / properties / noticeman / properties

Added value: +{
+  "attachments": {
+    "items": {
+      "properties": {
+        "fileSize": {
+          "maximum": 9007199254740991,
+          "minimum": 1,
+          "type": "integer"
+        },
+        "filename": {
+          "minLength": 1,
+          "type": "string"
+        },
+        "hash": {
+          "minLength": 1,
+          "type": "string"
+        }
+      },
+      "required": [
+        "filename",
+        "hash"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "externalAttachments": {
+    "items": {
+      "properties": {
+        "filename": {
+          "minLength": 1,
+          "type": "string"
+        },
+        "hash": {
+          "type": "string"
+        },
+        "id": {
+          "minLength": 1,
+          "type": "string"
+        },
+        "type": {
+          "minLength": 1,
+          "pattern": "EVIDENCE|REPORT|REPORT_PACKAGE",
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "type",
+        "filename"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "limitResponse": {
+    "maximum": 720,
+    "minimum": 0,
+    "type": "integer"
+  },
+  "notificationType": {
+    "enum": [
+      "ACCEPTED_OR_NOT",
+      "RECEIVED_AGREE",
+      "LONG_RESPONSE",
+      "NO_RESPONSE"
+    ],
+    "type": "string"
+  },
+  "parameters": {
+    "additionalProperties": {
+      "type": "string"
+    },
+    "propertyNames": {
+      "type": "string"
+    },
+    "type": "object"
+  },
+  "receiver": {
+    "items": {
+      "properties": {
+        "address": {
+          "format": "email",
+          "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"
+        },
+        "addressReplyTo": {
+          "format": "email",
+          "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"
+        },
+        "type": {
+          "enum": [
+            "TO",
+            "CC",
+            "BCC"
+          ],
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "minItems": 1,
+    "type": "array"
+  },
+  "reminder": {
+    "maximum": 720,
+    "minimum": 24,
+    "type": "integer"
+  },
+  "scheduledAt": {
+    "format": "date-time",
+    "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$",
+    "type": "string"
+  },
+  "sender": {
+    "properties": {
+      "address": {
+        "format": "email",
+        "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"
+      },
+      "addressReplyTo": {
+        "format": "email",
+        "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"
+      },
+      "name": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "subject": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "template": {
+    "type": "string"
+  }
+}

addedInput schema / properties / data / properties / noticeman / required
```
Added value: +[
+  "receiver",
+  "subject",
+  "notificationType"
+]
```
addedInput schema / properties / data / properties / noticeman / type
```
Added value: +"object"
```

changedInput schema / properties / data / properties / rcs / properties / scheduleDate / pattern

Previous value: -"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$"New value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$"

removedInput schema / properties / data / properties / smtp / properties / receiver / items / allOf

Removed value: -[
-  {
-    "properties": {
-      "address": {
-        "format": "email",
-        "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
-        "type": "string"
-      },
-      "addressReplyTo": {
-        "format": "email",
-        "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
-        "type": "string"
-      },
-      "name": {
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "properties": {
-      "metadata": {
-        "additionalProperties": {
-          "type": "string"
-        },
-        "propertyNames": {
-          "type": "string"
-        },
-        "type": "object"
-      },
-      "phone": {
-        "type": "string"
-      },
-      "type": {
-        "enum": [
-          "TO",
-          "CC",
-          "BCC"
-        ],
-        "type": "string"
-      }
-    },
-    "type": "object"
-  }
-]

addedInput schema / properties / data / properties / smtp / properties / receiver / items / properties

Added value: +{
+  "address": {
+    "format": "email",
+    "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"
+  },
+  "addressReplyTo": {
+    "format": "email",
+    "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"
+  },
+  "type": {
+    "enum": [
+      "TO",
+      "CC",
+      "BCC"
+    ],
+    "type": "string"
+  }
+}

addedInput schema / properties / data / properties / smtp / properties / receiver / items / type
```
Added value: +"object"
```

changedInput schema / properties / data / properties / smtp / properties / sender / properties / address / pattern

Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"

changedInput schema / properties / data / properties / smtp / properties / sender / properties / addressReplyTo / pattern

Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"

changedInput schema / properties / requestId / description

Previous value: -"UUID of the notification request. Obtain from notification_request_create."New value: +"OPTIONAL. Supply a UUID here only if you want to choose the new request's id yourself; omit it and the API assigns one. Either way this call RETURNS the requestId that every other Notification tool then requires — do not try to obtain it beforehand."

First observedv1.3.1Aug 5, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations only indicate readOnlyHint=false, idempotentHint=false, and destructiveHint=false. The description adds meaningful behavior context: it creates a draft, may auto-send on activation if autosend is true, and returns requestId plus notificationIds. There is no contradiction with the annotations.

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

Conciseness5/5

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

Three sentences, front-loaded with purpose and sequencing, then key parameter behavior and return values. No filler or redundancy; every sentence earns its place.

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 complex tool with a very rich schema, the description covers the essential lifecycle context, the autosend decision point, and the return contract. It does not enumerate provider-specific fields, but the schema supplies those structural details, so the description is largely sufficient for selecting and initially invoking the tool.

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?

Schema description coverage is only 17%, so the description must compensate, but it only meaningfully explains autosend and requestId. It does not clarify the large `data` object, provider-specific configuration, required `language`, `content`, or `metadata`, leaving the agent under-informed for a complex payload.

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 ('Creates a new notification request (draft)'), identifies the resource (top-level container for receivers and attachments), and immediately distinguishes it from siblings like notification_request_send, notification_receiver_add, and notification_document_add by saying 'Use this first'.

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?

Explicitly says when to use it ('before any other Notification-manager tool'), states there are no prerequisites, and contrasts autosend behavior with manually calling notification_request_send later. This gives an agent clear routing and sequencing guidance.

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

Deploy Server