Skip to main content
Glama
RhombusSystems

Rhombus MCP Server

Official

automated-prompts-tool

Manage automated chatbot prompts that run at scheduled intervals: create, update, delete, list, inspect, and page through stored responses. Control response visibility and verify job scheduling.

Instructions

This tool manages Rhombus MIND automated prompts - scheduled chatbot jobs that run a prompt at a recurring interval and store each response. Use it to list, inspect, create, update, delete, page through past responses for, share, or re-verify the schedule of an automated prompt.

Modes (set "requestType"):

  • list: List all automated prompts in the org. Optional 'lastEvaluatedKey' / 'maxPageSize' for pagination.

  • get: Get a single automated prompt's settings. Requires 'promptUuid'.

  • create: Create a new automated prompt. Requires 'prompt', 'invokeAt' (ISO 8601 with offset, must be at least 15 minutes in the future), 'frequencyValue', 'frequencyUnit', and 'permissionGroupUuid'. Optional 'responseTemplate' and 'notifyUserUuids'.

  • update: Selectively update an automated prompt. Requires 'promptUuid'; only the fields you set will be changed. To change the role, the caller must have access to both the current and new role. Pass an empty 'notifyUserUuids' array to clear notifyees.

  • delete: Delete an automated prompt and all of its stored responses. Requires 'promptUuid'.

  • get-history: Page through responses generated by an automated prompt. Requires 'promptUuid'. Optional 'lastEvaluatedKey' / 'maxPageSize'.

  • share-response: Update the visibility of one stored response. Requires 'chatUuid' and 'visibility' (PUBLIC, ORG_WIDE, SELECT_USERS, PRIVATE).

  • verify-scheduled: Re-verify that the job is scheduled to trigger; the server reschedules it if missing. Requires 'promptUuid'.

Notes:

  • Use 'user-tool' to look up user UUIDs and resolve them to names/emails. 'notifyUserUuids' must be members of the chosen 'permissionGroupUuid'.

  • 'invokeAt' is an ISO 8601 timestamp; both 'Z' and '+/-HH:mm' offsets are accepted. The tool converts it to milliseconds for the API.

  • Timestamps in the output are ISO 8601 strings with timezone offset (defaults to America/Los_Angeles when no org timezone is available).

  • 'submitTestPrompt' is intentionally not exposed by this tool.

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 automated prompt request to make.
promptUuidYesUUID of the automated prompt. Required for 'get', 'update', 'delete', 'get-history', and 'verify-scheduled'.
chatUuidYesUUID of a chat record (an individual response generated by an automated prompt). Required for 'share-response'.
visibilityYesVisibility for a shared chat response. Required for 'share-response'. One of PUBLIC, ORG_WIDE, SELECT_USERS, PRIVATE.
promptYesThe prompt MIND will execute every time the job runs. Required for 'create', recommended for 'update'.
responseTemplateYesOptional template that guides the shape of MIND's response. Used by 'create' and 'update'.
frequencyValueYesHow many time units between runs (e.g. 1 for 'every 1 day'). Required for 'create' alongside frequencyUnit.
frequencyUnitYesUnit for the recurrence (HOURS, DAYS, WEEKS, MONTHS). Required for 'create' alongside frequencyValue.
invokeAtYesWhen the automated prompt should first run. Required for 'create'. Must be at least 15 minutes in the future. 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.
permissionGroupUuidYesUUID of the permission group/role that owns the job. Users in this role (or a higher role) can view and edit the job, and MIND uses this role's permissions when running the prompt. Required for 'create'.
notifyUserUuidsYesUser UUIDs to email-notify when MIND finishes a run. These users must be members of the permission group set above. Used by 'create' and 'update'. Pass an empty array to clear existing notifyees on 'update'.
lastEvaluatedKeyYesPagination cursor returned by a previous 'list' or 'get-history' call. Pass to fetch the next page.
maxPageSizeYesMaximum number of items per page for 'list' and 'get-history'.
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
settingsNoReturned by 'get', 'create', and 'update'.
settingsListNoReturned by 'list'.
lastEvaluatedKeyNoPagination cursor for the next page; absent when no more pages.
chatHistoryNoReturned by 'get-history'.
verifyResultNoReturned by 'verify-scheduled'. Schedule expression and timezone for the next trigger.
successNoReturned by 'delete' and 'share-response'.
errorNoAn error message if the request failed.
Behavior4/5

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

No annotations provided, so the description carries full burden. It discloses that deleting removes stored responses, timestamps are ISO 8601, and includes warnings about large responses with filtering options. It lacks details on rate limits or auth requirements, but overall is transparent.

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 with clear sections (overview, modes, notes, output filtering) and front-loaded with a summary. It is thorough but not overly verbose; every sentence adds value.

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 (15 parameters, conditional requirements, multiple modes), the description is highly complete. It explains each mode's parameters, pagination, output filtering, and edge cases. Output schema exists, so return values need not be described.

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?

Schema coverage is 100%, but the description adds significant value beyond the schema: it explains conditional requirements (e.g., invokeAt must be 15+ minutes future), relationships between parameters (notifyUserUuids must be in permissionGroupUuid), and usage of pagination cursors.

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 automated prompts with explicit verbs like list, inspect, create, update, delete, page, share, verify. It distinguishes itself from sibling tools by focusing solely on automated prompts, with no overlap in purpose.

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 provides detailed usage guidance for each mode, including required and optional parameters, pagination, and a note to use 'user-tool' for UUID lookup. It does not explicitly state when not to use this tool, but the alternative is clear given its unique functionality.

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