Skip to main content
Glama
RhombusSystems

Rhombus MCP Server

Official

camera-uptime-tool

Analyze camera uptime and reliability over a time period. Compute uptime percentages, outage counts, and longest outage durations for one camera or your entire fleet.

Instructions

This tool analyzes camera uptime and reliability over a time period. It computes uptime percentages, outage counts, and longest outage durations.

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

  • get-camera-uptime: Get uptime statistics for a single camera. Requires cameraUuid, startTimeSec, and endTimeSec.

  • get-fleet-uptime: Get uptime statistics for ALL cameras in the organization, sorted by worst uptime first. Includes a fleet-wide summary with averages. Requires startTimeSec and endTimeSec.

startTimeSec and endTimeSec are UNIX timestamps in seconds.

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 uptime request to make.
cameraUuidYesCamera UUID. Required for 'get-camera-uptime'.
startTimeSecYesStart time as UNIX timestamp in seconds. Required for all requests.
endTimeSecYesEnd time as UNIX timestamp in seconds. Required for all requests.
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
cameraUptimeNoUptime stats for a single camera
fleetUptimeNoUptime stats for all cameras in the fleet, sorted by worst uptime first
fleetSummaryNoFleet-wide uptime summary
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. It thoroughly discloses the tool's behavior: computes statistics, requires timestamps, enumerates modes, and warns about large responses with advice on includeFields/filterBy. The only minor gap is not explicitly stating that it is a read-only operation.

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 into sections (summary, modes, timestamps, output filtering). It is slightly verbose due to repeated examples for filterBy/includeFields, but overall it is efficient and front-loaded with the core purpose.

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 (6 params, enums, large responses) and the presence of an output schema (not shown but declared), the description is largely complete. It covers all modes, parameter requirements, and output filtering. It does not detail the exact return fields, but that is acceptable since an output schema exists.

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%, but the description adds value by explaining how parameters relate to modes (cameraUuid required only for get-camera-uptime), specifying that startTimeSec and endTimeSec are UNIX timestamps, and reiterating the filterBy/includeFields usage with detailed examples and warnings.

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 analyzes camera uptime and reliability, computing uptime percentages, outage counts, and longest outage durations. It distinguishes two specific modes (single camera vs fleet), which helps the agent differentiate 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 Guidelines3/5

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

The description explicitly defines when to use each mode (single camera vs fleet), but it lacks guidance on when to prefer this tool over similar tools (e.g., 'camera-tool' for broader camera data). No when-not-to-use or alternative recommendations are provided.

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