@smartytalent/mcp-tools 0.7.5 → 0.7.7

package/dist/tools.json

@@ -22737,6 +22737,15 @@
                   "description": "Color theme for the notification avatar",
                   "default": "primary"
                 },
+                "messageKey": {
+                  "type": "string",
+                  "description": "Identifier of the message to render, e.g. `user.pendingApproval`. The bell looks it up in the client's own dictionaries and substitutes messageParams, so the sentence is produced in whatever language the reader has set AT DISPLAY TIME - switching language re-renders the whole history, and adding a platform language needs no backend change and no migration of stored rows. Same shape the mobile platforms use natively (APNs loc-key/loc-args, FCM loc_key/loc_args). Absent on producers that have not migrated yet; `title`/`subtitle` remain the English fallback, so a client that does not recognise a key must fall back to them rather than render nothing."
+                },
+                "messageParams": {
+                  "type": "object",
+                  "additionalProperties": true,
+                  "description": "Variable parts of the message, substituted into the dictionary entry for messageKey - e.g. {name, email} for `user.pendingApproval`. Names must match what the client dictionary expects: a mismatch surfaces as an untranslated placeholder, so the agreed keys and parameter names belong in the FE task, not in tribal memory."
+                },
                 "created": {
                   "type": "string",
                   "format": "date-time",
@@ -22752,21 +22761,37 @@
             "relationships": {
               "title": "NotificationRelationshipsSchema",
               "type": "object",
+              "description": "Declared in the WIRE shape, not the storage shape. Rows keep to-many entries as arrays, but transform_all_relationships serialises `users` to-ONE (RELATIONSHIP_TYPES says cardinality one) and renames it `user` - a spec written from the row therefore matches nothing and the generated client silently drops the whole relationship.",
               "properties": {
-                "users": {
+                "user": {
                   "type": "object",
+                  "description": "Who the notification is FOR. Singular and to-one on the wire.",
                   "properties": {
                     "data": {
-                      "type": "array",
-                      "items": {
-                        "type": "object",
-                        "properties": {
-                          "type": {
-                            "type": "string"
-                          },
-                          "id": {
-                            "type": "string"
-                          }
+                      "type": "object",
+                      "properties": {
+                        "type": {
+                          "type": "string"
+                        },
+                        "id": {
+                          "type": "string"
+                        }
+                      }
+                    }
+                  }
+                },
+                "subject": {
+                  "type": "object",
+                  "description": "What the notification is ABOUT - the target of the bell's deep link. Always this name, whatever the resource is, and it carries its own `type` so the client routes on that. Producers used to key this by resource type (`tasks`, `jobs`, ...), which cannot be declared here without enumerating every type any producer might ever use, so the typed client dropped all of them; it also collided with `user` outright when the subject was itself a user, overwriting the recipient. Absent when the notification is about nothing in particular.",
+                  "properties": {
+                    "data": {
+                      "type": "object",
+                      "properties": {
+                        "type": {
+                          "type": "string"
+                        },
+                        "id": {
+                          "type": "string"
                         }
                       }
                     }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@smartytalent/mcp-tools",
-  "version": "0.7.5",
+  "version": "0.7.7",
   "description": "MCP tool definitions for SmartyTalent API",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",