Skip to main content
Glama
RhombusSystems

Rhombus MCP Server

Official
by RhombusSystems
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

guest-management-tool

Retrieve guest lists with check-in status, activity logs, and sign-in records filtered by location and time range.

Instructions

This tool manages Rhombus guest/visitor operations. It can list all guests, retrieve activity logs, and filter activities by location.

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

  • get-all-guests: List all guests across the organization with their check-in status, host, company, and contact info.

  • get-activity-logs: Get org-wide guest activity logs (sign-ins, sign-outs). Supports optional time range filtering via startTimeMs/endTimeMs.

  • get-activities-for-location: Get guest activity logs for a specific location. Requires locationUuid. Supports optional time range filtering.

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 guest management request to make.
locationUuidYesLocation UUID. Required for 'get-activities-for-location'.
startTimeMsYesStart time filter in milliseconds since epoch. Optional for activity queries.
endTimeMsYesEnd time filter in milliseconds since epoch. Optional for activity queries.
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
guestsNoList of guests in the organization
activitiesNoList of guest activity log entries
errorNoAn error message if the request failed.

Tool Definition Quality

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that responses can exceed 400k characters and provides filtering mechanisms. It implies read-only operations (listing, retrieving logs) without stating destructive effects, which is appropriate.

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 modes enumerated in bullet points, but it is somewhat lengthy. Every sentence adds value, including the warnings about large responses. Could be slightly more concise, but structure is good.

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

Completeness5/5

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

Given the complexity (three modes, six parameters, output schema exists), the description covers all essential aspects: modes, required parameters, optional time filters, and output filtering. The warning about large responses is critical. Output schema existence reduces need to describe return values.

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. The description adds context about the three request types and explains the filterBy and includeFields parameters with examples and warnings, providing value beyond the schema.

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 manages Rhombus guest/visitor operations and lists three specific modes (get-all-guests, get-activity-logs, get-activities-for-location), each with a clear purpose. It distinguishes from sibling tools by the guest management focus.

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 explains when to use each mode based on the requestType parameter and provides filtering guidance (includeFields, filterBy) to handle large responses. It doesn't explicitly state when not to use this tool vs alternatives, but the context is sufficient.

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