Skip to main content
Glama
RhombusSystems

Rhombus MCP Server

Official

alarm-monitoring-tool

Retrieve armed/disarmed alarm monitoring status for all locations or a specific location, and get threat case details filtered by time and limits.

Instructions

This tool retrieves alarm monitoring status and threat case information across Rhombus locations.

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

  • org-status: Get the armed/disarmed alarm monitoring status for ALL locations in the organization in a single call.

  • get-threat-cases: Retrieve alarm monitoring threat cases (security incidents). Supports filtering by time range and max results.

  • location-status: Get detailed alarm monitoring status for a specific location. Requires locationUuid.

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 alarm monitoring request to make.
locationUuidYesLocation UUID. Required for 'location-status'.
startTimeMsYesFilter threat cases after this timestamp (ms since epoch). Optional for 'get-threat-cases'.
endTimeMsYesFilter threat cases before this timestamp (ms since epoch). Optional for 'get-threat-cases'.
maxResultsYesMaximum number of threat cases to return. Optional for 'get-threat-cases'.
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
locationStatusesNoAlarm monitoring status for each location
threatCasesNoList of alarm monitoring threat cases
locationDetailNoDetailed alarm monitoring status for a single location
errorNoAn error message if the request failed.
Behavior4/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 warns about large response sizes exceeding 400k characters and explains output filtering parameters to mitigate this. However, it does not explicitly state whether the tool is read-only or mention any other behavioral traits like authentication requirements or rate limits.

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

Conciseness5/5

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

The description is well-structured with clear sections for each mode and output filtering. It is concise, front-loading the core purpose and modes, and every sentence adds value (e.g., warnings about large responses). No unnecessary repetition or filler.

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 that the tool has an output schema, the description does not need to detail return values. It covers all parameters, modes, and provides important warnings about response size. It lacks information about error conditions or prerequisites (e.g., whether a location UUID is required for location-status), but overall it is sufficiently complete for a multi-mode retrieval tool.

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

Parameters5/5

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

The input schema has 100% description coverage for all 7 parameters, but the description adds significant value by explaining the modes of operation driven by requestType, detailing the output filtering parameters (includeFields and filterBy) with examples, and warning about large responses. This goes well beyond the schema descriptions.

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 it retrieves alarm monitoring status and threat case information, with specific modes (org-status, get-threat-cases, location-status) that differentiate the tool's capabilities. It uses specific verbs ('retrieves') and resources ('alarm monitoring status and threat case information'), making its purpose unambiguous and distinct from siblings.

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 explicitly lists the three modes of operation and explains when each should be used based on the requestType parameter. It provides context for each mode but does not explicitly advise when not to use this tool or suggest alternatives among sibling tools.

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