Skip to main content
Glama
RhombusSystems

Rhombus MCP Server

Official

rules-tool

Create, list, update, delete automation rules and retrieve event trigger history to trigger notifications, recordings, or actions based on camera, sensor, and door events.

Instructions

This tool manages Rhombus automation rules for triggering actions based on events.

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

  • list: List all automation rules in the organization.

  • create: Create a new automation rule. Requires ruleName and ruleConfig (JSON string with the rule definition).

  • update: Update an existing rule. Requires ruleUuid and ruleConfig (JSON string with updated fields).

  • delete: Delete a rule. Requires ruleUuid.

  • get-records: Get the event trigger history for a specific rule. Requires ruleUuid.

Rules can trigger notifications, recordings, and other actions based on events from cameras, sensors, doors, etc.

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 rules operation to perform.
ruleUuidYesThe UUID of the rule. Required for 'update', 'delete', and 'get-records'.
ruleNameYesThe name of the rule. Required for 'create'.
ruleConfigYesJSON string of the rule configuration. Required for 'create' and 'update'. Contains the rule definition.
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
rulesNoList of rules
ruleNoResult of create/update/delete operation
ruleRecordsNoRule trigger event records
errorNoAn error message if the request failed.
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that create/update require JSON config and that responses can be large, but it does not specify side effects (e.g., whether updates are idempotent, if deletion is permanent), authentication requirements, or potential errors. More detail would improve transparency.

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 clear list of modes followed by output filtering details. It front-loads the purpose and uses bullet-like formatting for readability. However, it could be slightly more concise by merging redundant warnings about response size.

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

Completeness4/5

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

Given the tool's complexity (5 modes, 6 params) and the presence of an output schema, the description covers the essential operational modes and parameter roles. It lacks information about prerequisites (e.g., permissions) and error handling, but overall it provides sufficient context for an agent to select and invoke the tool correctly.

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?

The input schema has 100% coverage, so parameters are already described. The description adds value by grouping parameters by mode (e.g., list requires no ruleUuid) and clarifying output filtering parameters' purpose. It also explains that ruleConfig is a JSON string for rule definition, beyond the schema's basic description.

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

Purpose5/5

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

The description clearly states the tool manages Rhombus automation rules for triggering actions based on events. It lists specific modes (list, create, update, delete, get-records) and provides context that rules can trigger notifications, recordings, etc. This distinguishes it from sibling tools like camera-tool or events-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?

The description explains each mode of operation and when to use each one, including required parameters per mode. It also warns about large responses and recommends using includeFields and filterBy. However, it does not explicitly state when NOT to use this tool or compare it to alternatives.

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