Skip to main content
Glama
RhombusSystems

Rhombus MCP Server

Official

door-schedule-exception-tool

Create, update, delete, and find one-time door schedule exceptions that override normal lock/unlock schedules for specific dates and times.

Instructions

This tool manages Rhombus door schedule exceptions. A door lock/unlock exception is a one-time rule used to change an access controlled door's locked/unlocked state. If a lock/unlock exception is enabled, it will overwrite the existing lock/unlock schedule. A schedule exception allows you to create a custom schedule that is only active for the specified dates/times. Once the date/time a schedule exception is set for passes, the original schedule will resume.

Door schedule exceptions can be either expired or not expired. If its scheduled date is in the past, then it is expired. Users through the web console can toggle whether to see expired door schedule exceptions or not. Please mirror this behavior when responding to the user.

It has the following modes of operation, determined by the "requestType" parameter:

  • create-exception: Create a door schedule exception. Requires exception (DoorScheduleExceptionType object). If locationUuid is missing but doorUuids are provided, the tool will resolve the location automatically.

  • delete-exception: Delete a door schedule exception. Requires exceptionUuid.

  • find-exceptions: Find door schedule exceptions across the organization, optionally filtered by date range.

  • find-exceptions-for-location: Find door schedule exceptions for a location. Requires locationUuid. Supports optional date range filters.

  • find-exceptions-for-door: Find door schedule exceptions for a door. Requires doorUuid. Supports optional date range filters.

  • get-exception: Get a single door schedule exception by UUID. Requires exceptionUuid.

  • update-exception: Update a door schedule exception. Requires exception (DoorScheduleExceptionType object). If intervals are omitted but defaultState and date range are provided, the tool will generate a full-day interval.

Use get-entity-tool to look up location and door UUIDs when needed.

Output filtering (all tools):

  • includeFields (string[]): Dot-notation paths to keep in the response (e.g. "vehicleEvents.vehicleLicensePlate"). Omit to return all fields.

  • filterBy (array): Predicates to filter array items. Each entry: {field, op, value} where op is one of = != > >= < <= contains. All conditions are ANDed. Example: [{field:"vehicleLicensePlate", op:"=", value:"ABC123"}] WARNING: some tool responses exceed 400k characters — use these params to request only the data you need.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestTypeYesThe type of door schedule exception request to make.
exceptionUuidYesDoor schedule exception UUID. Required for 'get-exception' and 'delete-exception'.
locationUuidYesLocation UUID. Required for 'find-exceptions-for-location'.
doorUuidYesDoor UUID. Required for 'find-exceptions-for-door'.
exceptionYesDoorScheduleExceptionType object. Required for 'create-exception' and 'update-exception'.
localStartDateRangeStartNoOptional date range filter (inclusive) for local start date beginning (yyyy-MM-dd).
localStartDateRangeEndNoOptional date range filter (inclusive) for local start date end (yyyy-MM-dd).
localEndDateRangeStartNoOptional date range filter (inclusive) for local end date beginning (yyyy-MM-dd).
localEndDateRangeEndNoOptional date range filter (inclusive) for local end date end (yyyy-MM-dd).
includeFieldsYesDot-notation field paths to include in the response (e.g. "vehicleEvents.vehicleLicensePlate"). Pass null to return all fields. WARNING: some responses can exceed 400k characters — use includeFields to request only the data you need. For high-volume tools this may be required to get a complete answer.
filterByYesFilter array items in the response by field values. All conditions are ANDed. Example: [{field: "vehicleLicensePlate", op: "=", value: "ABC123"}, {field: "confidence", op: ">", value: 0.8}] Use alongside includeFields to get only the specific records and fields you need.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
exceptionNoSingle door schedule exception result.
exceptionsNoList of door schedule exceptions.
deletedNoDelete result.
expiredACDLicensesDoorUuidsNoDoor UUIDs with expired access control licenses.
unassignedACDLicensesDoorUuidsNoDoor UUIDs with unassigned access control licenses.
warningMsgNoWarning returned by backend, if any.
errorNoAn error message if the request failed.
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses that exceptions overwrite existing schedules temporarily, that expired exceptions are in the past, and that omitting intervals can generate full-day intervals. Since no annotations exist, the description adequately covers behavior without contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a general overview, mode list, and output filtering section. While thorough, some repetition (e.g., definition of expired) lengthens it slightly without significant loss.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is highly complete given the tool's complexity. It explains the domain (schedule exceptions), all modes, parameter relationships, output filtering, and response size warnings. No gaps are apparent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All input parameters have schema descriptions (100% coverage). The description adds valuable context beyond the schema, such as automatic location resolution when missing and default interval generation. This goes above the baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it manages door schedule exceptions and enumerates all modes of operation with specific actions. It differentiates from siblings by focusing on temporary schedule overrides, but does not explicitly contrast with other tools like door-tool or access-control-tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when-to-use guidance for each requestType, explains automatic location resolution, references get-entity-tool for UUID lookups, and notes mirroring web console behavior for expired exceptions. Lacks explicit when-not-to-use instructions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/RhombusSystems/rhombus-node-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server