Skip to main content
Glama
RhombusSystems

Rhombus MCP Server

Official

search-tool

Search Rhombus camera footage and events by license plate, object color, text description, or motion events. Filter results with time ranges and camera selection.

Instructions

This tool performs visual and data searches across Rhombus camera footage and events.

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

  • license-plate: Search for license plate sightings by plate number. Requires query (the plate number or partial match).

  • object-by-color: Search for objects by color in camera footage. Requires query (color name) and cameraUuid.

  • object-by-text: Semantic search for objects in footage using a text description. Requires query (text description).

  • motion-search: Search for motion events in a camera's field of view. Requires cameraUuid, startTime, and endTime.

All search types support optional startTime and endTime to narrow the search window. Use the get-entity-tool with entityType CAMERA to get camera 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 search to perform.
queryYesThe search query string. Required for 'license-plate' (plate number), 'object-by-text' (text description of object), 'object-by-color' (color name).
cameraUuidYesThe UUID of the camera to search. Required for 'motion-search' and 'object-by-color'.
startTimeYesStart time for the search range.Time format is in ISO 8601 format. Both UTC ("2025-08-04T20:54:27.123Z") and time zone offsets ("2025-08-04T13:54:27.123-07:00") are accepted to ensure an unambiguous point in time.
endTimeYesEnd time for the search range.Time format is in ISO 8601 format. Both UTC ("2025-08-04T20:54:27.123Z") and time zone offsets ("2025-08-04T13:54:27.123-07:00") are accepted to ensure an unambiguous point in time.
deviceUuidsYesOptional list of device UUIDs to filter search results.
locationUuidsYesOptional list of location UUIDs to filter search results.
timeZoneYesThe timezone for formatting timestamps.
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
licensePlateResultsNoLicense plate search results
objectColorResultsNoObject color search results
objectTextResultsNoObject text search results
motionResultsNoMotion search results
errorNoAn error message if the request failed.
Behavior3/5

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

No annotations are provided, so the description must cover behavioral traits. It discloses that responses can exceed 400k characters and suggests using includeFields/filterBy. It does not mention rate limits, authentication needs, or side effects, which is acceptable for a read-only search tool.

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-organized with bullet points and clear sections. It is detailed but could be slightly more concise by reducing redundancy (e.g., repeating the warning about large responses). Overall, it is effective.

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 (10 params, multiple modes, output schema exists), the description covers operation modes, parameter requirements, and output filtering. It does not explain the return structure, but the output schema handles that. It is mostly complete for agent use.

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%, so baseline is 3. The description adds value by specifying which parameters are required per requestType, and provides examples and warnings for includeFields and filterBy, which goes beyond the schema's 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 explicitly states it performs visual and data searches across Rhombus camera footage and events, with four distinct modes of operation. This clearly identifies the tool's purpose and differentiates it from sibling tools like lpr-tool or camera-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 clearly outlines when to use each mode by specifying required parameters. It advises using get-entity-tool to obtain camera UUIDs and warns about large response sizes. However, it does not explicitly state when NOT to use this tool (e.g., for simpler lookups).

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