@velaro/mcp-server 0.6.66 → 0.6.67

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@velaro/mcp-server",
-  "version": "0.6.66",
+  "version": "0.6.67",
   "description": "Velaro MCP server — connect Claude and other AI agents directly to your Velaro account: KB, workflows, bots, conversations, contacts, routing, and more.",
   "type": "module",
   "bin": {

package/server.js

@@ -3989,15 +3989,16 @@ For multiSelect dynamic options: the variable named in dynamicOptionsVariable mu
   // Moshky AI safety rule and ConversationTriageService's prompt assembly (velaro-messaging).
   {
     name: 'focus_get_triage_rules',
-    description: 'Get this site\'s current AI triage rules: which of the 5 fixed labels (urgent, needs_reply, offer, fyi, waiting) are enabled, plus the per-channel triage-on-off and priority weight already owned by the channel-config endpoint, shown here for context. A label missing/never configured defaults to enabled.',
+    description: 'Get this site\'s current AI triage rules: which of the 5 fixed labels (urgent, needs_reply, offer, fyi, waiting) are enabled, plus the per-channel triage-on-off and priority weight already owned by the channel-config endpoint, shown here for context. A label missing/never configured defaults to enabled. Also returns triageMode ("off" or "economy").',
     inputSchema: { type: 'object', properties: {} },
   },
   {
     name: 'focus_update_triage_rules',
-    description: 'Enable or disable one or more of the 5 fixed AI triage labels (urgent, needs_reply, offer, fyi, waiting) for this site. Apply-if-present -- only labels included are changed. Rejects any label name outside the fixed set. Disabling all 5 fails safe back to all-enabled server-side rather than breaking triage.',
+    description: 'Enable or disable one or more of the 5 fixed AI triage labels (urgent, needs_reply, offer, fyi, waiting) for this site. Apply-if-present -- only labels included are changed. Rejects any label name outside the fixed set. Disabling all 5 fails safe back to all-enabled server-side rather than breaking triage. Optionally set triageMode: "economy" classifies obvious messages (auto-replies, clear urgency) without an AI call, lowering AI usage; "off" keeps current behavior. Unspecified fields are preserved.',
     inputSchema: {
       type: 'object',
       properties: {
+        triageMode: { type: 'string', enum: ['off', 'economy'], description: 'Optional. "economy" skips the AI call for obvious messages; "off" (default) keeps current behavior.' },
         labels: {
           type: 'array',
           description: 'Labels to update.',
@@ -4011,7 +4012,6 @@ For multiSelect dynamic options: the variable named in dynamicOptionsVariable mu
           },
         },
       },
-      required: ['labels'],
     },
   },
 
@@ -8776,10 +8776,17 @@ async function handleTool(name, args) {
     case 'focus_get_triage_rules':
       return await messagingGet('/Focus/triage-rules');
     case 'focus_update_triage_rules': {
-      if (!Array.isArray(args.labels) || args.labels.length === 0) {
-        throw new Error('labels is required and must be a non-empty array.');
+      const hasLabels = Array.isArray(args.labels) && args.labels.length > 0;
+      const hasMode = args.triageMode !== undefined && args.triageMode !== null;
+      if (!hasLabels && !hasMode) {
+        throw new Error('Provide labels (non-empty array) and/or triageMode.');
       }
-      const body = args.labels.map((l) => ({ Label: l.label, Enabled: l.enabled }));
+      if (hasMode && !['off', 'economy'].includes(args.triageMode)) {
+        throw new Error('triageMode must be "off" or "economy".');
+      }
+      const labels = hasLabels ? args.labels.map((l) => ({ Label: l.label, Enabled: l.enabled })) : undefined;
+      // Legacy array body when only labels are sent; object body when triageMode is involved.
+      const body = hasMode ? { ...(labels ? { labels } : {}), triageMode: args.triageMode } : labels;
       return await messagingPut('/Focus/triage-rules', body);
     }