rhombus-node-mcp 0.1.56 → 0.1.57

package/dist/types/time-conversion-tool-types.js

@@ -1,8 +1,7 @@
 import { z } from "zod";
 export const TOOL_ARGS = {
-    time_to_convert: z.union([
-        z.string(),
-        z.number(),
-    ]).describe("The time to convert. This can be either an ISO 8601 timestamp string (e.g., '2023-10-05T14:48:00.000Z') or a Unix timestamp in milliseconds."),
+    time_to_convert: z
+        .union([z.string(), z.number()])
+        .describe("The time(s) to convert. Either an ISO 8601 timestamp string (e.g. '2023-10-05T14:48:00.000Z' or '2023-10-05T14:48:00-07:00'), a Unix timestamp in milliseconds, or a comma-separated list of several such values (converted in order)."),
 };
 const TOOL_ARGS_SCHEMA = z.object(TOOL_ARGS);

package/dist/types/update-tool-types.js

@@ -1,14 +1,15 @@
 import { z } from "zod";
-// Define the entity types that can be updated
-export const ENTITY_TYPE = z.enum([
-    "camera",
-    "climate-sensor",
-    "door-controller",
-    "environmental-gateway",
-    "audio-gateway",
-    "doorbell-camera",
-    "badge-reader",
-]);
+/**
+ * The entity types this tool can actually update.
+ *
+ * Deliberately narrow. It previously listed climate-sensor, door-controller,
+ * environmental-gateway, audio-gateway and badge-reader, none of which had a
+ * handler — every one returned "not yet implemented. Coming soon!". Because the
+ * chatbot adapts MCP tools with `strict: false`, an enum is advisory: nothing
+ * stopped the model picking one of those, and each attempt burned a turn on a
+ * guaranteed dead end. Add a value here only once its handler exists.
+ */
+export const ENTITY_TYPE = z.enum(["camera", "doorbell-camera"]);
 // Camera-specific update schemas
 export const CameraVideoSettings = z.object({
     hdr_enabled: z.boolean().optional().describe("Enable HDR (High Dynamic Range)"),
@@ -20,7 +21,7 @@ export const CameraVideoSettings = z.object({
         .describe("Image brightness adjustment (-255 to 255)"),
     img_contrast: z.number().min(0).max(128).optional().describe("Image contrast (0 to 128)"),
     img_saturation: z.number().min(0).max(255).optional().describe("Image saturation (0 to 255)"),
-    img_sharpness: z.number().min(0).max(255).optional().describe("Image sharpness (0 to 255)"),
+    img_sharpness: z.number().min(0).max(11).optional().describe("Image sharpness (0 to 11; 6 works for most situations)"),
     resolution: z
         .object({
         width: z.number().int().positive().optional(),
@@ -59,9 +60,9 @@ export const CameraVideoSettings = z.object({
     night_img_sharpness: z
         .number()
         .min(0)
-        .max(255)
+        .max(11)
         .optional()
-        .describe("Night mode sharpness (0 to 255)"),
+        .describe("Night mode sharpness (0 to 11; 6 works for most situations)"),
 });
 export const CameraAudioSettings = z.object({
     audio_record: z.boolean().optional().describe("Enable audio recording"),
@@ -95,21 +96,37 @@ export const CameraDeviceSettings = z.object({
 });
 // Input schema for the tool
 export const TOOL_ARGS = {
-    entityType: ENTITY_TYPE.describe("Type of entity to update"),
-    entityUuid: z.string().nullable().describe("UUID of the entity to update"),
+    entityType: ENTITY_TYPE.describe("Type of entity to update. Only 'camera' and 'doorbell-camera' can be updated through this tool; " +
+        "for climate sensors, door controllers, environmental gateways, audio gateways and badge readers, tell the " +
+        "user the change has to be made in the Rhombus Console rather than attempting it here."),
+    entityUuid: z
+        .string()
+        .nullable()
+        .describe('UUID of the entity to update. Faceted UUIDs are supported (e.g. "cameraUuid.v0" / "cameraUuid.v1") to target a specific camera facet; defaults to "v0" when no facet is given.'),
     // Camera-specific update fields
+    // These three arrive as free-form JSON strings, so the field schemas below are
+    // NOT part of the input schema the model sees — this description text is the
+    // only range guidance it ever gets. Keep it in sync with CameraVideoSettings /
+    // CameraAudioSettings / CameraDeviceSettings.
+    //
+    // Promoting them to real object schemas would NOT make out-of-range values
+    // impossible: the chatbot sends MCP tools to OpenAI with `strict: false`
+    // (chatbot src/mcp/toolAdapters.ts), so there is no constrained decoding, and
+    // even under `strict: true` JSON Schema `minimum`/`maximum` are not enforced
+    // keywords. Range checking is therefore ALWAYS the tool's job — which is why
+    // parseSettingsBlock reports the field, the bound, and the received value.
     cameraVideoSettings: z
         .string()
         .nullable()
-        .describe("JSON string of video settings to update for camera"),
+        .describe(`JSON string of video settings to update for camera. Values outside these ranges are REJECTED — img_brightness: -255 to 255 · img_contrast: 0 to 128 · img_saturation: 0 to 255 · img_sharpness: 0 to 11 (6 is typical — NOT a 0-100 scale) · wdr_strength: 0 to 128 (64 is typical) · zero_motion_video_bitrate_percent: 0 to 100 · hdr_enabled / wdr_enabled / video_persist_disabled: booleans · resolution: {"width": n, "height": n}. The night-mode fields (night_img_brightness, night_img_contrast, night_img_saturation, night_img_sharpness) take the same ranges as their daytime counterparts. Example for a dark image: '{"img_brightness": 0, "wdr_strength": 64}'; for a washed-out image: '{"img_brightness": -50, "img_contrast": 80}'; for a blurry image: '{"img_sharpness": 8}'. Saturation matters — 0 yields grayscale; most cameras look best mid-range, tune from there.`),
     cameraAudioSettings: z
         .string()
         .nullable()
-        .describe("JSON string of audio settings to update for camera"),
+        .describe(`JSON string of audio settings to update for camera. audio_record / device_mic_enabled / device_speaker_enabled: booleans · audio_internal_mic_volume: 0 to 100 · audio_internal_speaker_volume: 0 to 100. Example: '{"audio_record": true, "audio_internal_mic_volume": 80}'.`),
     cameraDeviceSettings: z
         .string()
         .nullable()
-        .describe("JSON string of device settings to update for camera"),
+        .describe(`JSON string of device settings to update for camera (name, timezone, LED). camera_name / camera_timezone: strings · led_intensity: 0 to 100 · led_mode: one of "auto", "always_on", "always_off" · led_stealth_mode: boolean. LED control uses EXACTLY these underscore field names (not camelCase): LED off = '{"led_stealth_mode": true}' (recommended) or '{"led_mode": "always_off"}'; LED on = '{"led_stealth_mode": false}' or '{"led_mode": "always_on"}' or '{"led_mode": "auto"}'.`),
     // Step tracking for multi-step updates
     step: z
         .enum(["entity-selection", "settings-configuration", "confirmation"])
@@ -129,6 +146,11 @@ export const OUTPUT_SCHEMA = z.object({
     success: z.boolean().optional(),
     error: z.string().optional(),
     updatedSettings: z.any().optional(),
+    // Doorbell writes are verified by reading /doorbellcamera/getConfig back;
+    // these carry the before values and anything the read-back contradicted.
+    previousSettings: z.any().optional(),
+    settingsNotApplied: z.any().optional(),
+    settingsNotVerified: z.any().optional(),
 });
 // API payload types
 export const UpdateCameraConfigPayload = z.object({

package/dist/types/user-tool-types.js

@@ -5,6 +5,9 @@ export var UserToolRequestType;
     UserToolRequestType["FIND_BY_EMAIL"] = "find-by-email";
     UserToolRequestType["GET_PERMISSIONS"] = "get-permissions";
     UserToolRequestType["GET_PERMISSION_GROUPS"] = "get-permission-groups";
+    UserToolRequestType["CREATE_USER"] = "create-user";
+    UserToolRequestType["UPDATE_USER"] = "update-user";
+    UserToolRequestType["DELETE_USER"] = "delete-user";
 })(UserToolRequestType || (UserToolRequestType = {}));
 // NOTE: `includeFields` and `filterBy` are NOT declared here — the
 // `createFilteringProxy` wrapper automatically injects them into every tool's
@@ -15,7 +18,27 @@ export const TOOL_ARGS = {
     email: z
         .string()
         .nullable()
-        .describe("The email address of the user to find. Required for 'find-by-email'."),
+        .describe("The email address of the user. Required for 'find-by-email' and 'create-user'. For 'create-user' this is where the invitation is sent, so read it back to the user before creating — a typo invites a stranger into the organization."),
+    userUuid: z
+        .string()
+        .nullable()
+        .describe("The UUID of the user. Required for 'update-user' and 'delete-user'. Get it from 'list-users' or 'find-by-email' — do not guess one."),
+    userName: z
+        .string()
+        .nullable()
+        .describe("The user's display name. Required for 'create-user'; for 'update-user' it is the new name (omit to leave it unchanged)."),
+    permissionGroupUuid: z
+        .string()
+        .nullable()
+        .describe("UUID of the permission group (role) to assign. Required for 'create-user'; for 'update-user' it is the new role (omit to leave the role unchanged). Get it from 'get-permission-groups' with includeFields ['permissionGroups.uuid','permissionGroups.name','permissionGroups.description']. A role decides what the person can see and do, so confirm the role NAME with the user rather than picking one."),
+    suppressWelcomeEmail: z
+        .boolean()
+        .nullable()
+        .describe("Only for 'create-user'. Creating a user emails them an invitation by default. Set true only when the user explicitly asks not to notify the new person."),
+    confirmDelete: z
+        .boolean()
+        .nullable()
+        .describe("Required to be true for 'delete-user'. Deleting a user revokes their console access and their credentials, and cannot be undone, so it refuses without explicit confirmation."),
 };
 const TOOL_ARGS_SCHEMA = z.object(TOOL_ARGS);
 // Permission level assigned to a resource for a role. Typed loosely as string
@@ -106,5 +129,25 @@ export const OUTPUT_SCHEMA = z.object({
         .array(PermissionGroupSchema)
         .optional()
         .describe("List of permission groups in the organization."),
+    created: z
+        .object({ success: z.boolean().optional(), uuid: z.string().optional() })
+        .optional()
+        .describe("Result of 'create-user'."),
+    updated: z
+        .object({ success: z.boolean().optional(), uuid: z.string().optional() })
+        .optional()
+        .describe("Result of 'update-user'."),
+    deleted: z
+        .object({ success: z.boolean().optional(), uuid: z.string().optional() })
+        .optional()
+        .describe("Result of 'delete-user'."),
+    note: z
+        .string()
+        .optional()
+        .describe("A caveat about this result that the user needs to be told."),
+    warningMsg: z
+        .string()
+        .optional()
+        .describe("A warning from the Rhombus API — the call succeeded, but with a caveat."),
     error: z.string().optional().describe("An error message if the request failed."),
 });

package/dist/types/video-walls-tool-types.js

@@ -28,9 +28,21 @@ export const CreateVideoWallOptions = z
     .describe("The options for creating a video wall. This is required if your requestType === `create`");
 export const TOOL_ARGS = {
     requestType: z
-        .enum(["list", "create"])
+        .enum(["list", "create", "update", "delete"])
         .describe("The type of request to make."),
     videoWallCreateOptions: CreateVideoWallOptions,
+    videoWallUuid: z
+        .string()
+        .nullable()
+        .describe("The uuid of the video wall to act on. Required for `update` and `delete`. Get it from `list` — do not guess one."),
+    displayName: z
+        .string()
+        .nullable()
+        .describe("Only for `update`: a new name for the wall. Omit to leave the name unchanged."),
+    deviceList: z
+        .array(z.string())
+        .nullable()
+        .describe("Only for `update`: the camera uuids the wall should contain AFTER the update. This REPLACES the wall's current cameras rather than adding to them, so include the ones being kept. To add or remove a few, read the wall with `list` first and send the full resulting set. The grid layout is recomputed from the new count."),
     includeFields: INCLUDE_FIELDS_ARG,
     filterBy: FILTER_BY_ARG,
 };
@@ -53,7 +65,23 @@ export const OUTPUT_SCHEMA = z.object({
         .optional(),
     videoWall: z
         .array(z.any())
-        .describe("If requestType is `get`, then this field will be populated with the video wall.")
+        .describe("Unused — no current requestType populates this field. Use `videoWalls` (from 'list') or `uuid` (from 'create').")
         .optional(),
     uuid: z.string().describe("The uuid of the created video wall.").optional(),
+    updated: z
+        .object({ success: z.boolean().optional(), uuid: z.string().optional() })
+        .optional()
+        .describe("Result of an `update` request."),
+    deleted: z
+        .object({ success: z.boolean().optional(), uuid: z.string().optional() })
+        .optional()
+        .describe("Result of a `delete` request."),
+    note: z
+        .string()
+        .optional()
+        .describe("A caveat about this result that the user needs to be told."),
+    warningMsg: z
+        .string()
+        .optional()
+        .describe("A warning from the Rhombus API — the call succeeded, but with a caveat."),
 });