Skip to main content
Glama
RhombusSystems

Rhombus MCP Server

Official

entity-lookup-tool

Look up specific devices by their UUIDs to get exact device states, licenses, and features. Filter results to limit response size and include only needed data.

Instructions

Retrieves specific entities (or devices) by their UUIDs. Takes a list of device UUIDs and returns the device information for those specific devices. Use this tool when the user asks for details on devices' states and details about their licenses and features. The return structure is a JSON object that contains the states of the requested entities. This data is exact. Only devices with matching UUIDs will be returned.

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
deviceUuidsYesThe UUIDs of the devices to look up.
timeZoneYesThe timezone for formatting timestamps. This is necessary for the tool to produce accurate formatted timestamps.
tempUnitYesThe unit of temperature to return, if applicable. Default is Celsius.
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
camerasNoList of cameras matching the provided UUIDs
camerasCountNoNumber of cameras found
doorbellCamerasNoList of doorbell cameras matching the provided UUIDs
doorbellCamerasCountNoNumber of doorbell cameras found
badgeReadersNoList of badge readers matching the provided UUIDs
badgeReadersCountNoNumber of badge readers found
accessControlledDoorsNoList of access controlled doors matching the provided UUIDs
accessControlledDoorsCountNoNumber of access controlled doors found
audioGatewaysNoList of audio gateways matching the provided UUIDs
audioGatewaysCountNoNumber of audio gateways found
doorStatesNoList of door sensors matching the provided UUIDs
doorStatesCountNoNumber of door sensors found
climateStatesNoList of environmental sensors matching the provided UUIDs
climateStatesCountNoNumber of environmental sensors found
occupancySensorStatesNoList of motion sensors matching the provided UUIDs
occupancySensorStatesCountNoNumber of motion sensors found
buttonStatesNoList of buttons matching the provided UUIDs
buttonStatesCountNoNumber of buttons found
keypadStatesNoList of keypads matching the provided UUIDs
keypadStatesCountNoNumber of keypads found
minimalEnvironmentalGatewayStatesNoList of environmental gateways matching the provided UUIDs
minimalEnvironmentalGatewayStatesCountNoNumber of environmental gateways found
errorNoAn error message if the request failed.
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses exactness ('Only devices with matching UUIDs will be returned') and large response warnings, but omits safety, idempotency, or permission details.

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?

Two concise paragraphs: first states purpose, second provides critical output filtering guidance. Front-loaded main 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?

Explains return structure as JSON of device states. Output schema exists so full detail isn't needed. Covers essential usage aspects.

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 description coverage is 100%, baseline 3. Description adds extra value beyond schema by warning about 400k character responses and advising use of includeFields/filterBy.

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 entities by UUIDs and returns device information including licenses and features, distinguishing it from sibling tools like search-tool which do free-text search.

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?

Provides explicit context: 'Use this tool when the user asks for details on devices' states and details about their licenses and features.' Lacks explicit when-not-to-use but the context is clear.

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