@hailer/mcp 0.1.6 → 0.1.9

package/dist/mcp/tools/insight.js

@@ -21,31 +21,65 @@ const logger = (0, logger_1.createLogger)({ component: 'insight-tools' });
 // ============================================================================
 /**
  * Field definition schema - either meta field or custom fieldId
+ * Accepts both 'id' and 'fieldId' for flexibility (LLMs often use 'id')
  */
 const fieldSchema = zod_1.z.object({
     name: zod_1.z.string().describe("Column name in SQL query"),
-}).and(zod_1.z.union([
-    zod_1.z.object({
-        meta: zod_1.z.enum([
-            '_id',
-            'uid',
-            'team',
-            'createdBy',
-            'name',
-            'created',
-            'updated',
-            'phaseId',
-            'phaseName',
-            'phaseLastMove',
-            'workflowId',
-            'workflowName',
-            'priority'
-        ]).describe("Built-in activity property"),
-    }),
-    zod_1.z.object({
-        fieldId: zod_1.z.string().describe("Custom field ID from workflow"),
-    }),
-]));
+    // Accept both 'id' and 'fieldId' - will be normalized to 'fieldId'
+    id: zod_1.z.string().optional().describe("Field ID (alias for fieldId)"),
+    fieldId: zod_1.z.string().optional().describe("Custom field ID from workflow"),
+    meta: zod_1.z.enum([
+        '_id',
+        'uid',
+        'team',
+        'createdBy',
+        'name',
+        'created',
+        'updated',
+        'phaseId',
+        'phaseName',
+        'phaseLastMove',
+        'workflowId',
+        'workflowName',
+        'priority'
+    ]).optional().describe("Built-in activity property (alternative to fieldId)"),
+}).refine((data) => data.meta || data.fieldId || data.id, { message: "Field must have either 'meta', 'fieldId', or 'id'" });
+/**
+ * Sanitize field name to be SQL-identifier safe (no spaces, special chars)
+ */
+function sanitizeFieldName(name) {
+    // Convert to camelCase: "Injury Type" -> "InjuryType", "Expected Recovery" -> "ExpectedRecovery"
+    return name
+        .split(/\s+/)
+        .map((word, index) => {
+        if (index === 0)
+            return word.charAt(0).toLowerCase() + word.slice(1);
+        return word.charAt(0).toUpperCase() + word.slice(1);
+    })
+        .join('')
+        .replace(/[^a-zA-Z0-9_]/g, ''); // Remove any remaining special chars
+}
+/**
+ * Normalize field definitions: convert 'id' to 'fieldId' and sanitize names
+ */
+function normalizeFields(sources) {
+    return sources.map(source => ({
+        ...source,
+        fields: source.fields.map(field => {
+            let normalized = { ...field };
+            // Sanitize field name (remove spaces, make SQL-safe)
+            if (normalized.name) {
+                normalized.name = sanitizeFieldName(normalized.name);
+            }
+            // If 'id' is provided but not 'fieldId', use 'id' as 'fieldId'
+            if (field.id && !field.fieldId && !field.meta) {
+                const { id, ...rest } = normalized;
+                return { ...rest, fieldId: id };
+            }
+            return normalized;
+        }),
+    }));
+}
 /**
  * Source definition schema - workflow as SQL table
  */
@@ -57,22 +91,7 @@ const sourceSchema = zod_1.z.object({
 // ============================================================================
 // CREATE INSIGHT TOOL
 // ============================================================================
-const createInsightDescription = `🧪 [PLAYGROUND] Create SQL-like insights (workflows = tables, activities = rows, fields = columns)
-
-⚠️ **MANDATORY: YOU MUST LOAD SKILL FIRST**
-**BEFORE calling this tool, you are REQUIRED to:**
-1. Load the skill: \`get_skill({ skillName: "create-insight-skill" })\`
-2. Read the query examples, JOIN patterns, and aggregation examples
-3. Test your SQL with \`preview_insight\` first
-**FAILURE TO LOAD THE SKILL FIRST IS AN ERROR**
-
-**Required Parameters**:
-- name: Insight name
-- sources: Array with name (table alias), workflowId, fields (meta or fieldId)
-- query: Standard SQL (SELECT, JOIN, WHERE, GROUP BY, ORDER BY, LIMIT)
-
-**Meta Fields**: _id, uid, team, createdBy, name, created, updated, phaseId, phaseName, phaseLastMove, workflowId, workflowName, priority
-**SQL Support**: All standard SQL features including JOINs and aggregations`;
+const createInsightDescription = `Create SQL insight over workflow data (workflows=tables, activities=rows, fields=columns)`;
 exports.createInsightTool = {
     name: 'create_insight',
     group: tool_registry_1.ToolGroup.PLAYGROUND,
@@ -118,11 +137,13 @@ exports.createInsightTool = {
                 name: args.name,
                 sourcesCount: args.sources.length
             });
+            // Normalize sources (convert 'id' to 'fieldId' if needed)
+            const normalizedSources = normalizeFields(args.sources);
             // Build insight payload
             const insightData = {
                 name: args.name,
                 public: args.public || false,
-                sources: args.sources,
+                sources: normalizedSources,
                 query: args.query,
             };
             // Call v3.insight.create endpoint
@@ -233,21 +254,7 @@ exports.createInsightTool = {
 // ============================================================================
 // PREVIEW INSIGHT TOOL
 // ============================================================================
-const previewInsightDescription = `🧪 [PLAYGROUND] Preview insight - Test SQL on ~20 activities before saving
-
-⚠️ **MANDATORY: YOU MUST LOAD SKILL FIRST**
-**BEFORE calling this tool, you are REQUIRED to:**
-1. Load the skill: \`get_skill({ skillName: "preview-insight-skill" })\`
-2. Read the debugging tips and security notes
-3. Understand the SQL testing patterns
-**FAILURE TO LOAD THE SKILL FIRST IS AN ERROR**
-
-**Purpose**: Debug SQL syntax, test JOINs, verify field mappings without creating insight
-
-**Required Parameters**:
-- sources: Same format as create_insight (name, workflowId, fields)
-- query: SQL query to test
-- insightId (optional): Test changes to existing insight`;
+const previewInsightDescription = `Test SQL query on sample data before creating/updating insight`;
 exports.previewInsightTool = {
     name: 'preview_insight',
     group: tool_registry_1.ToolGroup.PLAYGROUND,
@@ -288,9 +295,11 @@ exports.previewInsightTool = {
                 sourcesCount: args.sources.length,
                 insightId: args.insightId
             });
+            // Normalize sources (convert 'id' to 'fieldId' if needed)
+            const normalizedSources = normalizeFields(args.sources);
             // Build preview payload
             const previewData = {
-                sources: args.sources,
+                sources: normalizedSources,
                 query: args.query,
                 ...(args.insightId && { insightId: args.insightId }),
             };
@@ -362,33 +371,7 @@ exports.previewInsightTool = {
 // ============================================================================
 // GET INSIGHT DATA TOOL
 // ============================================================================
-const getInsightDataDescription = `🧪 [PLAYGROUND] Get Insight Data - Execute insight and retrieve results
-
-**What is Get Insight Data?**
-Executes a saved insight's SQL query and returns the complete results. Unlike preview (limited to ~20 rows), this returns all matching activities.
-
-**When to Use**:
-- Get full results from a saved insight
-- Export insight data
-- Verify insight after creation
-- Check updated data after changes
-
-**Example - Basic Usage**:
-\`\`\`javascript
-get_insight_data({
-  insightId: '<insight-id>'
-})
-\`\`\`
-
-**Update Option**:
-- \`update: false\` (default) - Returns cached results (faster)
-- \`update: true\` - Recalculates from current activity data (slower but fresh)
-
-**Tips**:
-- Use \`update: true\` if activity data has changed
-- Results can be large - may take time for big datasets
-- Use \`preview_insight\` first to test queries
-- Get insight ID from \`create_insight\` or \`list_insights\``;
+const getInsightDataDescription = `Execute insight and get results`;
 exports.getInsightDataTool = {
     name: 'get_insight_data',
     group: tool_registry_1.ToolGroup.PLAYGROUND,
@@ -484,51 +467,7 @@ exports.getInsightDataTool = {
 // ============================================================================
 // UPDATE INSIGHT TOOL
 // ============================================================================
-const updateInsightDescription = `🧪 [PLAYGROUND] Update Insight - Modify existing insight properties
-
-**What it does:**
-Updates an existing insight's properties (name, query, sources, visibility).
-
-**Required Parameters:**
-- insightId - The insight ID to update
-
-**Optional Parameters (include only what you want to change):**
-- name - New insight name
-- public - Change visibility (true/false)
-- sources - Updated workflow sources
-- query - Updated SQL query
-
-**Example - Update name only:**
-\`\`\`javascript
-update_insight({
-  insightId: '<insight-id>',
-  name: 'New Insight Name'
-})
-\`\`\`
-
-**Example - Update query:**
-\`\`\`javascript
-update_insight({
-  insightId: '<insight-id>',
-  query: 'SELECT * FROM players WHERE position = "Forward"'
-})
-\`\`\`
-
-**Example - Full update:**
-\`\`\`javascript
-update_insight({
-  insightId: '<insight-id>',
-  name: 'Updated Insight',
-  public: true,
-  sources: [{ name: 'p', workflowId: 'xxx', fields: [...] }],
-  query: 'SELECT * FROM p'
-})
-\`\`\`
-
-**Tips:**
-- Use \`preview_insight\` to test query changes before updating
-- Use \`list_insights\` to find insight IDs
-- Only include fields you want to change`;
+const updateInsightDescription = `Update existing insight (name, query, sources, or visibility)`;
 exports.updateInsightTool = {
     name: 'update_insight',
     group: tool_registry_1.ToolGroup.PLAYGROUND,
@@ -572,7 +511,7 @@ exports.updateInsightTool = {
                 updateData.public = args.public;
             }
             if (args.sources !== undefined) {
-                updateData.sources = args.sources;
+                updateData.sources = normalizeFields(args.sources);
             }
             if (args.query !== undefined) {
                 updateData.query = args.query;
@@ -672,46 +611,7 @@ exports.updateInsightTool = {
 // ============================================================================
 // REMOVE INSIGHT TOOL
 // ============================================================================
-const removeInsightDescription = `🧪 [PLAYGROUND] Remove Insight - ⚠️ DANGER: Permanently deletes insight and all its data
-
-⚠️ **MANDATORY: GATHER COMPLETE CONTEXT BEFORE CALLING THIS TOOL**
-**BEFORE calling this tool, you are REQUIRED to:**
-1. Load the skill: \`get_skill({ skillName: "remove-insight-skill" })\`
-2. Fetch insight details with \`list_insights\` to get:
-   - Insight name and ID
-   - Workspace ID and name
-   - SQL query
-   - Source workflows
-   - Number of sources
-3. Show comprehensive confirmation message including:
-   - Workspace ID and name
-   - Insight ID and name
-   - What will be deleted (definition, results, permissions, discussion)
-   - Sources being queried (workflows)
-   - Clear irreversibility warning
-4. Wait for explicit user confirmation
-**FAILURE TO GATHER AND SHOW THIS CONTEXT IS AN ERROR**
-
-**Required**: insightId
-**Permission**: Workspace administrator
-
-**What Gets Deleted**:
-- Insight definition (sources, query, name)
-- Saved query results
-- Insight permissions
-- Associated discussion
-
-**Example**:
-\`\`\`javascript
-remove_insight({
-  insightId: '<insight-id>'
-})
-\`\`\`
-
-**Tips**:
-- Use \`list_insights\` to find insight IDs
-- Use \`get_insight_data\` to verify before deleting
-- Operation cannot be undone - data is permanently lost`;
+const removeInsightDescription = `Delete insight permanently`;
 exports.removeInsightTool = {
     name: 'remove_insight',
     group: tool_registry_1.ToolGroup.NUCLEAR,
@@ -839,26 +739,7 @@ exports.removeInsightTool = {
 // ============================================================================
 // LIST INSIGHTS TOOL
 // ============================================================================
-const listInsightsDescription = `🧪 [PLAYGROUND] List Insights - View all insights in workspace
-
-**What are Insights?**
-Insights are SQL-like reports over Hailer workflow data. They allow querying activities like database tables.
-
-**Purpose**: List all insights in the workspace to find insight IDs.
-
-**Example**:
-\`\`\`javascript
-list_insights({
-  workspaceId: "optional-workspace-id"
-})
-\`\`\`
-
-**Response includes**:
-- Insight ID and name
-- SQL query
-- Sources (workflows being queried)
-- Public/private status
-- Created/updated timestamps`;
+const listInsightsDescription = `List all insights in workspace`;
 exports.listInsightsTool = {
     name: 'list_insights',
     group: tool_registry_1.ToolGroup.PLAYGROUND,
@@ -901,8 +782,11 @@ exports.listInsightsTool = {
                     responseText += `${index + 1}. **${insight.name}**\n`;
                     responseText += `   - Insight ID: \`${insight._id}\`\n`;
                     responseText += `   - Public: ${insight.public ? 'Yes' : 'No'}\n`;
-                    responseText += `   - Sources: ${insight.sources.length} workflow(s)\n`;
-                    responseText += `   - Query: \`${insight.query.substring(0, 80)}${insight.query.length > 80 ? '...' : ''}\`\n\n`;
+                    // Show source names (table aliases) - critical for SQL debugging
+                    const sourceNames = insight.sources?.map((s) => s.name).join(', ') || 'none';
+                    responseText += `   - Table names: \`${sourceNames}\` (use EXACTLY these in SQL FROM/JOIN)\n`;
+                    responseText += `   - Sources: ${insight.sources?.length || 0} workflow(s)\n`;
+                    responseText += `   - Query: \`${insight.query?.substring(0, 80)}${(insight.query?.length || 0) > 80 ? '...' : ''}\`\n\n`;
                 });
                 responseText += `💡 **Next Steps:**\n`;
                 responseText += `- Use \`get_insight_data\` to execute an insight\n`;

package/dist/mcp/tools/workflow.js

@@ -60,6 +60,7 @@ exports.getWorkflowSchemaTool = {
     schema: zod_1.z.object({
         workflowId: zod_1.z.string().describe("Workflow ID to get schema from"),
         phaseId: zod_1.z.string().describe("Phase ID to get schema from (use list_workflow_phases to get available phases)"),
+        compact: zod_1.z.boolean().optional().describe("Return compact summary instead of full field details (default: false)"),
     }),
     async execute(args, context) {
         try {
@@ -78,6 +79,21 @@ exports.getWorkflowSchemaTool = {
             // Get complete field definitions from workflow (includes keys and all metadata)
             const workflowFields = workflow.fields || {};
             const fieldsOrder = workflow.fieldsOrder || Object.keys(workflowFields);
+            // Compact mode: brief summary for chat agents WITH field IDs (required for insights)
+            if (args.compact) {
+                const fieldLines = fieldsOrder.map((fieldId) => {
+                    const field = workflowFields[fieldId];
+                    if (!field)
+                        return null;
+                    return `- ${field.label || 'Unnamed'} (${field.type}): fieldId="${fieldId}"`;
+                }).filter(Boolean);
+                return {
+                    content: [{
+                            type: "text",
+                            text: `📋 **${workflow.name}** (workflowId: ${args.workflowId})\n\n**Fields:**\n${fieldLines.join('\n')}`,
+                        }],
+                };
+            }
             let responseText = `📋 **WORKFLOW SCHEMA** for "${workflow.name}":\n\n`;
             if (schemaData.name) {
                 responseText += `**Name Field:**\n`;
@@ -336,45 +352,7 @@ exports.listWorkflowsTool = {
 // ============================================================================
 // TOOL 1: INSTALL WORKFLOW
 // ============================================================================
-const installWorkflowDescription = `🧪 [PLAYGROUND] Install workflow(s) from template
-
-⚠️ **MANDATORY: YOU MUST LOAD SKILL FIRST**
-**BEFORE calling this tool, you are REQUIRED to:**
-1. Load the skill: \`get_skill({ skillName: "install-workflow-skill" })\`
-2. Read the complete documentation
-3. Follow the examples and patterns shown in the skill
-**FAILURE TO LOAD THE SKILL FIRST IS AN ERROR**
-
-⚠️ COPY THIS EXACT STRUCTURE (modify values only):
-\`\`\`json
-{
-  "workflowTemplates": [{
-    "name": "My Workflow Name",
-    "fields": {
-      "_1000": { "label": "Title", "type": "text" }
-    },
-    "phases": {
-      "_2000": { "name": "To Do", "isInitial": true }
-    }
-  }]
-}
-\`\`\`
-
-**CRITICAL RULES (breaking these causes API rejection):**
-1. ✅ MUST wrap in \`workflowTemplates\` array
-2. ✅ MUST use objects for fields/phases: \`{ "_1000": {...} }\` NOT arrays \`[{...}]\`
-3. ✅ MUST use \`label\` in fields (NOT "name")
-4. ✅ MUST use \`data\` for options (NOT "options")
-5. ✅ MUST use template IDs: \`_0001\`, \`_1000\`, \`_2000\` (underscore + 4 digits)
-
-**Field properties allowed:**
-- \`label\` (required) - Display name
-- \`type\` (required) - Field type: text, date, numeric, textpredefinedoptions, activitylink
-- \`key\` (recommended) - API key for readable names
-- \`data\` (for dropdowns/links) - Array of options or workflow IDs
-- \`required\` (optional) - Boolean
-
-**Workflow = DB table, Fields = Columns, Activities = Rows**`;
+const installWorkflowDescription = `Install workflow from template`;
 const installWorkflowSchema = zod_1.z.object({
     workspaceId: zod_1.z
         .string()
@@ -534,27 +512,7 @@ exports.installWorkflowTool = {
 // ============================================================================
 // TOOL 2: REMOVE WORKFLOW
 // ============================================================================
-const removeWorkflowDescription = `🧪 [PLAYGROUND] Remove workflow - ⚠️ DANGER: Permanently deletes workflow, activities, and discussions
-
-⚠️ **MANDATORY: GATHER COMPLETE CONTEXT BEFORE CALLING THIS TOOL**
-**BEFORE calling this tool, you are REQUIRED to:**
-1. Load the skill: \`get_skill({ skillName: "remove-workflow-skill" })\`
-2. Fetch workflow details with \`list_workflows\` to get:
-   - Workflow name and ID
-   - Workspace ID and name
-   - Activity count
-   - Relationships (which workflows link to this one)
-3. Show comprehensive confirmation message including:
-   - Workspace ID and name
-   - Workflow ID and name
-   - Exact count of activities that will be deleted
-   - Impact analysis - which other workflows will be affected (broken activity links)
-   - Clear irreversibility warning
-4. Wait for explicit user confirmation
-**FAILURE TO GATHER AND SHOW THIS CONTEXT IS AN ERROR**
-
-**Required**: workflowId
-**Permission**: Workspace administrator`;
+const removeWorkflowDescription = `Delete workflow permanently`;
 const removeWorkflowSchema = zod_1.z.object({
     workflowId: zod_1.z
         .string()
@@ -695,35 +653,7 @@ exports.removeWorkflowTool = {
 // ============================================================================
 // TOOL 3: UPDATE WORKFLOW FIELD
 // ============================================================================
-const updateWorkflowFieldDescription = `🧪 [PLAYGROUND] Update workflow field - Modify field properties and configure function fields
-
-⚠️ **MANDATORY: YOU MUST LOAD SKILL FIRST**
-**BEFORE calling this tool, you are REQUIRED to:**
-1. Load the skill: \`get_skill({ skillName: "update-workflow-field-skill" })\`
-2. Read the examples and best practices
-3. Understand function fields and field type restrictions
-**FAILURE TO LOAD THE SKILL FIRST IS AN ERROR**
-
-**Required Parameters**:
-- workflowId: Workflow ID
-- fieldId: Field ID to update
-- fieldData: Properties to update (label, key, type, data, required, function, functionVariables, functionEnabled)
-
-**IMPORTANT - Updating Labels Only:**
-When updating ONLY the label (not the key), set \`autoGenerateKey: false\` to prevent key regeneration:
-- ✅ Correct: \`{ fieldData: { label: "Nationality" }, autoGenerateKey: false }\`
-- ❌ Wrong: \`{ fieldData: { label: "Nationality" } }\` (will try to regenerate key and may fail)
-
-**Auto-generate key**: When creating NEW keys, set label only and key auto-generates as camelCase ("Start Date" → "startDate")
-
-**Field Type Changes**: Avoid changing field types (text → country, etc.) as this may be restricted by the API
-
-**Use Cases**: Add keys, update labels, update activitylink targets, configure calculated fields, modify options
-
-**Examples**:
-- Update label only: \`update_workflow_field({ workflowId: "xxx", fieldId: "yyy", fieldData: { label: "New Label" }, autoGenerateKey: false })\`
-- Update label and options: \`update_workflow_field({ workflowId: "xxx", fieldId: "yyy", fieldData: { label: "Status", data: ["Active", "Inactive"] }, autoGenerateKey: false })\`
-- Add new key to field: \`update_workflow_field({ workflowId: "xxx", fieldId: "yyy", fieldData: { label: "My Field" }, autoGenerateKey: true })\` (generates key: "myField")`;
+const updateWorkflowFieldDescription = `Update workflow field properties`;
 const updateWorkflowFieldSchema = zod_1.z.object({
     workflowId: zod_1.z
         .string()
@@ -857,11 +787,7 @@ exports.updateWorkflowFieldTool = {
 // ============================================================================
 // TOOL 4: TEST FUNCTION FIELD
 // ============================================================================
-const testFunctionFieldDescription = `🧪 [PLAYGROUND] Test function field - Dry-run test function code against real activity before saving
-
-**Required**: activityId, fieldId, function (JavaScript accessing dep.variableName)
-**Returns**: Result value, resolved dependencies, execution stats, or detailed errors
-**Workflow**: Configure with update_workflow_field → test → fix → re-test → deploy`;
+const testFunctionFieldDescription = `Test function field code against activity`;
 const testFunctionFieldSchema = zod_1.z.object({
     activityId: zod_1.z
         .string()

package/dist/mcp/utils/hailer-api-client.d.ts

@@ -72,12 +72,14 @@ export declare class HailerApiClient {
     /**
      * Join an activity's discussion by following the activity - uses Socket API
      * This is the recommended way to join activity discussions.
-     * Returns true if now following, false if was already following and toggled off.
+     * Returns true if now following.
+     * IMPORTANT: activities.follow is a toggle, so if we accidentally toggle OFF, we toggle back ON.
      */
     joinActivityDiscussion(activityId: string): Promise<boolean>;
     /**
      * Leave an activity's discussion by unfollowing the activity - uses Socket API
-     * Returns true if successfully unfollowed, false if was already not following.
+     * Returns true if successfully unfollowed.
+     * IMPORTANT: activities.follow is a toggle, so if we accidentally toggle ON, we toggle back OFF.
      */
     leaveActivityDiscussion(activityId: string): Promise<boolean>;
     /**

package/dist/mcp/utils/hailer-api-client.js

@@ -218,25 +218,39 @@ class HailerApiClient {
     /**
      * Join an activity's discussion by following the activity - uses Socket API
      * This is the recommended way to join activity discussions.
-     * Returns true if now following, false if was already following and toggled off.
+     * Returns true if now following.
+     * IMPORTANT: activities.follow is a toggle, so if we accidentally toggle OFF, we toggle back ON.
      */
     async joinActivityDiscussion(activityId) {
-        // activities.follow toggles the state, but we need to check current state first
-        const activity = await this.fetchActivityById(activityId);
-        // If not already following, call activities.follow to join
+        // activities.follow TOGGLES the state:
+        // - returns true = now following (joined)
+        // - returns false = now NOT following (left)
         const result = await this.request('activities.follow', [activityId]);
-        return result; // true if now following, false if unfollowed
+        if (result === false) {
+            // Oops! We were already following and just toggled OFF (left).
+            // Toggle again to re-join.
+            this.logger.debug('Toggle resulted in unfollow, re-toggling to join', { activityId });
+            await this.request('activities.follow', [activityId]);
+        }
+        return true; // We're now following either way
     }
     /**
      * Leave an activity's discussion by unfollowing the activity - uses Socket API
-     * Returns true if successfully unfollowed, false if was already not following.
+     * Returns true if successfully unfollowed.
+     * IMPORTANT: activities.follow is a toggle, so if we accidentally toggle ON, we toggle back OFF.
      */
     async leaveActivityDiscussion(activityId) {
-        // activities.follow toggles the state
-        const activity = await this.fetchActivityById(activityId);
-        // If already following, call activities.follow to unfollow
+        // activities.follow TOGGLES the state:
+        // - returns true = now following (joined)
+        // - returns false = now NOT following (left)
         const result = await this.request('activities.follow', [activityId]);
-        return !result; // Inverse: true if now unfollowed, false if followed
+        if (result === true) {
+            // Oops! We were NOT following and just toggled ON (joined).
+            // Toggle again to leave.
+            this.logger.debug('Toggle resulted in follow, re-toggling to leave', { activityId });
+            await this.request('activities.follow', [activityId]);
+        }
+        return true; // We're now NOT following either way
     }
     /**
      * Leave a discussion directly - uses Socket API

package/dist/mcp-server.d.ts

@@ -16,6 +16,10 @@ export interface MCPServerConfig {
     port: number;
     corsOrigins: string[];
     toolRegistry: ToolRegistry;
+    getDaemonStatus?: () => Array<{
+        botId: string;
+        state: any;
+    }> | null;
 }
 export declare class MCPServerService {
     private app;

package/dist/mcp-server.js

@@ -65,10 +65,13 @@ class MCPServerService {
                 });
                 res.on('finish', () => {
                     const duration = Date.now() - start;
-                    requestLogger.info('Request completed', {
-                        statusCode: res.statusCode,
-                        duration
-                    });
+                    // Log at debug level for successful requests, info for errors
+                    if (res.statusCode >= 400) {
+                        requestLogger.info('Request failed', { statusCode: res.statusCode, duration });
+                    }
+                    else {
+                        requestLogger.debug('Request completed', { statusCode: res.statusCode, duration });
+                    }
                 });
             }
             // Add logger to request for route handlers
@@ -88,6 +91,22 @@ class MCPServerService {
             };
             res.json(health);
         });
+        // Daemon status endpoint - monitor LLM context
+        this.app.get('/daemon/status', (_, res) => {
+            if (!this.config.getDaemonStatus) {
+                res.status(404).json({ error: 'Daemon mode not enabled' });
+                return;
+            }
+            const status = this.config.getDaemonStatus();
+            if (!status) {
+                res.status(503).json({ error: 'Daemon not running' });
+                return;
+            }
+            res.json({
+                timestamp: new Date().toISOString(),
+                daemons: status
+            });
+        });
         // MCP Protocol endpoint - JSON-RPC 2.0 over SSE
         this.app.post('/api/mcp', async (req, res) => {
             req.logger.debug('MCP request received', { method: req.body?.method });
@@ -202,6 +221,7 @@ class MCPServerService {
         this.logger.info('Routes configured', {
             routes: [
                 '/health - Server health check',
+                '/daemon/status - Daemon context monitor',
                 '/api/mcp - MCP protocol (JSON-RPC 2.0)'
             ]
         });