Skip to main content
Glama
RhombusSystems

Rhombus MCP Server

Official

door-tool

Retrieve and create door controller rules and door policies for Rhombus access control systems. Use appropriate parameters to manage rules and policies.

Instructions

This tool manages Rhombus door controller rules and door policies.

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

  • get-door-controller-rules: Get all rules for a specific door controller. Requires doorControllerUuid.

  • create-door-controller-rule: Create a new rule for a door controller. Requires doorControllerUuid and ruleConfig (JSON string).

  • get-door-policies: Get all door alert policies in the organization.

  • create-door-policy: Create a new door policy. Requires policyName and policyConfig (JSON string).

Use the get-entity-tool to find door controller and access controlled door UUIDs.

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 operation to perform.
doorControllerUuidYesThe UUID of the door controller device. Required for 'get-door-controller-rules' and 'create-door-controller-rule'.
ruleConfigYesJSON string of the door controller rule configuration. Required for 'create-door-controller-rule'.
policyNameYesThe name for the new door policy. Required for 'create-door-policy'.
policyConfigYesJSON string of door policy configuration. Required for 'create-door-policy'.
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
doorControllerRulesNoList of door controller rules
createdRuleNoResult of creating a door controller rule
doorPoliciesNoList of door policies
createdPolicyNoResult of creating a door policy
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, the description carries the full burden. It explains the four modes and warns about large responses, but omits behavioral traits like error handling, idempotency of creation operations, required permissions, or side effects. This is a partial disclosure.

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 clear sections for modes and output filtering. It is front-loaded with the core purpose. Minor redundancy (e.g., repeating 'Requires' in each bullet) could be trimmed, but overall efficient.

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

Completeness3/5

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

Given the multi-mode complexity and presence of an output schema, the description covers the basics: modes, required params for each, and filtering. Missing context includes error conditions, dependency availability, and what the response contains for creation operations.

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?

Schema coverage is 100%, baseline 3. The description adds value by organizing parameters by requestType, explaining required dependencies, and providing examples for includeFields and filterBy. This goes beyond the schema's own descriptions.

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 Rhombus door controller rules and door policies, and lists four specific operation modes with required parameters. However, it does not explicitly differentiate this tool from sibling tools like 'rules-tool' or 'access-control-tool', which could cause confusion.

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

Usage Guidelines2/5

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

The description mentions using get-entity-tool to find UUIDs, but provides no guidance on when to use this tool versus other sibling tools (e.g., rules-tool for non-door rules). There is no 'when not to use' or alternative tool suggestions.

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