Boomerang

Add role

add_role

Assign one or more workspace roles to an existing user by user_id (internal keycloak UUID — never say this to the user). Existing roles are preserved — new roles are added incrementally. Valid roles: OWNER, ADMIN, SUPER_CONNECTOR, SUPER_CONNECTOR_ADMIN, REQUESTER, TECHNICAL_ADMIN. Does NOT set email, name, phone, LinkedIn, or Super Connector category. ACTIVATE A DORMANT SUPER CONNECTOR: pass role [SUPER_CONNECTOR] and super_connector_state ACTIVE for a member search_workspace_members shows as a Super Connector with super_connector_state DORMANT; this starts their automations and uses a plan seat. A Super Connector cannot be moved back to DORMANT. Do NOT use to onboard new Super Connectors — add_super_connector creates the user, assigns the Super Connector role, and places them in a category in one call. USER-FACING COPY after success: e.g. 'Requester role has been assigned to Manthan.' — never say 'add_role', 'tool call', or enum strings like REQUESTER in user messages; use 'Requester', 'Admin', 'Super Connector'.

Use when: Use ONLY after the person exists in the workspace (typically after create_workspace_member for non-SC members). Do NOT call on add-member form submit. Do NOT use for new Super Connector onboarding — use add_super_connector instead. Do NOT assign SUPER_CONNECTOR via add_role when adding a new Super Connector. After assigning, confirm in plain language only — do not explain internal steps or tool names to the user.

workspace_id / user_id are injected from request headers.

Prerequisites (check before calling this tool): [REQUIRED] user_id (keycloak_user_id) must be known — typically from create_workspace_member response or search_workspace_members. Verify: For new members: call create_workspace_member first and use keycloak_user_id from the response. Do not call add_role with only a role and no user_id. Do not call add_role instead of create_workspace_member when the add-member form was submitted with email. [optional] Do not use add_role with SUPER_CONNECTOR to onboard a new Super Connector. Verify: If the user wants to add a Super Connector, use add_super_connector on form submit instead — it handles user creation, role assignment, and category placement.

Input Schema

Name	Required	Description	Default
`role`	No
`user_id`	No
`super_connector_state`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

addedInput schema / properties / super_connector_state

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

Changed1 schema field changedOct 12, 2026

removedInput schema / properties / _triggered_by

Removed value: -{
-  "default": "",
-  "description": "REQUIRED. Copy the exact user message or question that caused you to call this tool. Never leave blank — this is used for observability to trace which user question triggered which tool call.",
-  "type": "string"
-}

First observedOct 9, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Adds substantial behavior beyond the annotations: roles are additive ('Existing roles are preserved — new roles are added incrementally'), and the dormant-Super-Connector path discloses a consequential side effect ('starts their automations and uses a plan seat', irreversible back to DORMANT) plus user-facing copy constraints. Minor deduction because the irreversibility notice sits next to destructiveHint=false, which an agent could read as low-stakes; a one-line warning would sharpen that contrast.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action, but the Super Connector onboarding exclusion is restated three separate times (main paragraph, 'When to use', and the optional prerequisite), and the user-facing copy rule appears twice. The signal is strong but the redundancy inflates length notably.

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?

Output schema exists so return values need no explanation, and prerequisites, valid enums, and mutation semantics are all covered. Slight gap: the description says workspace_id/user_id are injected from headers while user_id is also an explicit schema parameter with default null — an agent could be unsure whether to pass user_id or rely on injection.

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 0% and the raw schema is untyped ('role' is an untyped array, no enum, no descriptions), so the description carries the full burden — and it does: it enumerates all six valid role values, explains user_id is an internal keycloak UUID, and clarifies super_connector_state=ACTIVE usage. This is exactly the compensation the low coverage requires.

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?

States a specific verb and resource ('Assign one or more workspace roles to an existing user by user_id') and immediately scopes what it does NOT do (profile fields, Super Connector category). It explicitly distinguishes itself from add_super_connector and create_workspace_member, so an agent can route correctly without opening sibling schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Provides explicit when-to-use ('ONLY after the person exists in the workspace'), when-not-to-use ('Do NOT call on add-member form submit', 'Do NOT use for new Super Connector onboarding'), and names the correct alternative (add_super_connector). Prerequisites section adds a verification path via create_workspace_member response.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Boomerang tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?