@assetlab/mcp-server 2.0.1 → 2.2.0

package/dist/tools-write.js

@@ -128,6 +128,7 @@ export function registerWriteTools(server, client) {
         location_ids: ASSOCIATION_ARRAY_SCHEMA('Locations this work order covers — use instead of location_id when there is more than one. Sending location_id alone replaces this with that single id.'),
         asset_ids: ASSOCIATION_ARRAY_SCHEMA('Assets this work order covers — use instead of asset_id when there is more than one.'),
         system_ids: ASSOCIATION_ARRAY_SCHEMA('Systems this work order covers — resolve via list_systems. Systems have no singular field; this array is the only way to associate them.'),
+        infrastructure_asset_ids: ASSOCIATION_ARRAY_SCHEMA('Infrastructure features this work order covers — resolve via list_infrastructure_assets. Use this when one job covers several features (a round of hydrant flushing); the whole selection is one work order with one completion and one cost, split across the features. Mutually exclusive with asset/location/system targets.'),
         start_date: z.string().optional().describe('Start date (ISO 8601)'),
         due_date: z.string().optional().describe('Due date (ISO 8601)'),
         estimated_time: z.number().min(0).optional().describe('Estimated time in hours'),
@@ -142,7 +143,7 @@ export function registerWriteTools(server, client) {
             .string()
             .max(2000)
             .optional()
-            .describe('Image URL (upload via create_upload_url with bucket "attachments", then set this to the public_url)'),
+            .describe('Image storage path (upload via create_upload_url with bucket "attachments", then set this to the returned path)'),
         meter_reading: z
             .number()
             .min(0)
@@ -187,6 +188,7 @@ export function registerWriteTools(server, client) {
         location_ids: ASSOCIATION_ARRAY_SCHEMA('Locations this work order covers — use instead of location_id when there is more than one. Sending location_id alone replaces this with that single id.'),
         asset_ids: ASSOCIATION_ARRAY_SCHEMA('Assets this work order covers — use instead of asset_id when there is more than one.'),
         system_ids: ASSOCIATION_ARRAY_SCHEMA('Systems this work order covers — resolve via list_systems. Systems have no singular field; this array is the only way to associate them.'),
+        infrastructure_asset_ids: ASSOCIATION_ARRAY_SCHEMA('Infrastructure features this work order covers — resolve via list_infrastructure_assets. Use this when one job covers several features (a round of hydrant flushing); the whole selection is one work order with one completion and one cost, split across the features. Mutually exclusive with asset/location/system targets.'),
         start_date: z.string().optional().describe('Start date (ISO 8601)'),
         due_date: z.string().optional().describe('Due date (ISO 8601)'),
         estimated_time: z.number().min(0).optional().describe('Estimated time in hours'),
@@ -201,7 +203,7 @@ export function registerWriteTools(server, client) {
             .string()
             .max(2000)
             .optional()
-            .describe('Image URL (upload via create_upload_url with bucket "attachments", then set this to the public_url)'),
+            .describe('Image storage path (upload via create_upload_url with bucket "attachments", then set this to the returned path)'),
         meter_reading: z
             .number()
             .min(0)
@@ -924,6 +926,7 @@ export function registerWriteTools(server, client) {
         asset_ids: ASSOCIATION_ARRAY_SCHEMA('Assets this schedule covers — use instead of asset_id when there is more than one.'),
         system_ids: ASSOCIATION_ARRAY_SCHEMA('Systems this schedule covers. Systems have no singular field; this array is the only way to associate them.'),
         location_ids: ASSOCIATION_ARRAY_SCHEMA('Locations this schedule covers — use instead of location_id when there is more than one. Sending location_id alone replaces this with that single id.'),
+        infrastructure_asset_ids: ASSOCIATION_ARRAY_SCHEMA('Infrastructure features this schedule covers — resolve via list_infrastructure_assets. One schedule over several features generates one work order per cycle covering all of them. Mutually exclusive with asset/location/system targets.'),
         tasks: z
             .array(z.object({
             id: z.string().describe('Unique task ID (use a random string)'),
@@ -999,6 +1002,7 @@ export function registerWriteTools(server, client) {
         asset_ids: ASSOCIATION_ARRAY_SCHEMA('Assets this schedule covers — use instead of asset_id when there is more than one.'),
         system_ids: ASSOCIATION_ARRAY_SCHEMA('Systems this schedule covers. Systems have no singular field; this array is the only way to associate them.'),
         location_ids: ASSOCIATION_ARRAY_SCHEMA('Locations this schedule covers — use instead of location_id when there is more than one. Sending location_id alone replaces this with that single id.'),
+        infrastructure_asset_ids: ASSOCIATION_ARRAY_SCHEMA('Infrastructure features this schedule covers — resolve via list_infrastructure_assets. One schedule over several features generates one work order per cycle covering all of them. Mutually exclusive with asset/location/system targets.'),
         tasks: z
             .array(z.object({
             id: z.string().describe('Unique task ID'),
@@ -1918,6 +1922,56 @@ export function registerWriteTools(server, client) {
         }
     });
     // ============================================================
+    // 16b. Work Order Schedules (scope: work_order_schedules)
+    // ============================================================
+    server.tool('create_work_order_schedule', "Schedule a work order for a technician on a date (one entry of a day plan). stop_order gives the position in the technician's day; leave it unset for an unordered calendar entry. Requires work_order_schedules:write scope.", {
+        work_order_id: z.string().uuid().describe('Work order ID (required)'),
+        technician_id: z.string().min(1).describe('Technician Clerk user ID (required)'),
+        scheduled_date: z.string().describe('Date (YYYY-MM-DD, required)'),
+        scheduled_start_time: z.string().optional().describe('Start time (HH:MM)'),
+        scheduled_end_time: z.string().optional().describe('End time (HH:MM)'),
+        duration_minutes: z.number().int().optional().describe('Planned duration in minutes'),
+        stop_order: z.number().int().optional().describe('1-based stop position in the day plan'),
+        travel_time_minutes: z.number().int().optional().describe('Travel time from previous stop'),
+        scheduling_notes: z.string().optional().describe('Scheduling notes'),
+    }, async (params) => {
+        try {
+            const result = await client.create('work-order-schedules', buildBody(params));
+            return formatResult(result);
+        }
+        catch (err) {
+            return formatError(err);
+        }
+    });
+    server.tool('update_work_order_schedule', 'Update a work order schedule entry by ID (date, times, stop_order, notes). work_order_id is immutable. Requires work_order_schedules:write scope.', {
+        id: z.string().uuid().describe('Work order schedule ID'),
+        technician_id: z.string().min(1).optional().describe('Technician Clerk user ID'),
+        scheduled_date: z.string().optional().describe('Date (YYYY-MM-DD)'),
+        scheduled_start_time: z.string().optional().describe('Start time (HH:MM)'),
+        scheduled_end_time: z.string().optional().describe('End time (HH:MM)'),
+        duration_minutes: z.number().int().optional().describe('Planned duration in minutes'),
+        stop_order: z.number().int().optional().describe('1-based stop position in the day plan'),
+        travel_time_minutes: z.number().int().optional().describe('Travel time from previous stop'),
+        scheduling_notes: z.string().optional().describe('Scheduling notes'),
+    }, async ({ id, ...rest }) => {
+        try {
+            const result = await client.update('work-order-schedules', id, buildBody(rest));
+            return formatResult(result);
+        }
+        catch (err) {
+            return formatError(err);
+        }
+    });
+    server.tool('delete_work_order_schedule', "Delete a work order schedule entry by ID (removes the stop from the technician's day). Requires work_order_schedules:write scope.", { id: z.string().uuid().describe('Work order schedule ID') }, async ({ id }) => {
+        try {
+            const result = await client.remove('work-order-schedules', id);
+            return formatResult(result);
+        }
+        catch (err) {
+            return formatError(err);
+        }
+    });
+    // ============================================================
     // 17. Project Comments (scope: project_comments)
     // ============================================================
     server.tool('create_project_comment', 'Create a new comment on a project. Requires project_comments:write scope.', {
@@ -3151,7 +3205,7 @@ export function registerWriteTools(server, client) {
     // ============================================================
     // Upload URLs
     // ============================================================
-    server.tool('create_upload_url', 'Generate a signed upload URL for uploading a file to AssetLab storage. Returns a signed_url to PUT the file to, a public_url for referencing, and the path. IMPORTANT — When a user wants to upload a file, always clarify the target. File upload paths: (1) Asset IMAGE: bucket "asset-images" → update_asset with image_url. (2) Asset DOCUMENT (O&M, warranty, spec): bucket "documents" → create_asset_document. (3) Work order IMAGE: bucket "attachments" → update_work_order with image_url. (4) Work order/request/PM ATTACHMENT: bucket "attachments" → create_attachment with the parent ID. (5) Project DOCUMENT: bucket "project-documents" → create_project_document. (6) Contract DOCUMENT: bucket "contract-documents" → create_contract_document. Always ask the user which type they mean if ambiguous. Requires upload_urls:write scope.', {
+    server.tool('create_upload_url', 'Generate a signed upload URL for uploading a file to AssetLab storage. Returns a signed_url to PUT the file to, and the storage path to store on the record. IMPORTANT — When a user wants to upload a file, always clarify the target. File upload paths: (1) Asset IMAGE: bucket "asset-images" → update_asset with image_url. (2) Asset DOCUMENT (O&M, warranty, spec): bucket "documents" → create_asset_document. (3) Work order IMAGE: bucket "attachments" → update_work_order with image_url. (4) Work order/request/PM ATTACHMENT: bucket "attachments" → create_attachment with the parent ID. (5) Project DOCUMENT: bucket "project-documents" → create_project_document. (6) Contract DOCUMENT: bucket "contract-documents" → create_contract_document. Always ask the user which type they mean if ambiguous. Requires upload_urls:write scope.', {
         bucket: z
             .enum([
             'documents',
@@ -3171,7 +3225,7 @@ export function registerWriteTools(server, client) {
             return formatError(err);
         }
     });
-    server.tool('upload_file', 'Upload a file to AssetLab storage by sending its bytes inline (base64). The AssetLab backend performs the storage upload server-side — use this tool when the client cannot PUT directly to Supabase Storage (e.g. Claude integrations whose outbound network blocks arbitrary supabase.co hosts). Returns { path, public_url, bucket, file_size, content_type }. After uploading, pass path or public_url to the appropriate record tool (update_asset image_url, create_asset_document file_path, update_work_order image_url, create_attachment file_path, create_project_document file_path, create_contract_document file_path). Server limit is ~10 MB decoded; MCP arg ceiling effectively caps file size around 700 KB–1 MB. For larger files, use create_upload_url instead. Requires upload_urls:write scope.', {
+    server.tool('upload_file', 'Upload a file to AssetLab storage by sending its bytes inline (base64). The AssetLab backend performs the storage upload server-side — use this tool when the client cannot PUT directly to Supabase Storage (e.g. Claude integrations whose outbound network blocks arbitrary supabase.co hosts). Returns { path, bucket, file_size, content_type }. After uploading, pass path to the appropriate record tool (update_asset image_url, create_asset_document file_path, update_work_order image_url, create_attachment file_path, create_project_document file_path, create_contract_document file_path). Server limit is ~10 MB decoded; MCP arg ceiling effectively caps file size around 700 KB–1 MB. For larger files, use create_upload_url instead. Requires upload_urls:write scope.', {
         bucket: z
             .enum([
             'documents',