QuintaDB

add_user_to_team_group

Add a person to a team group by email. An account is created when there is none. The new account gets a password of its own, which only the invitation letter shows (with a one-time link that signs the person in); the answer's invitation says what was mailed. Never tell anyone a password. move_from_other_groups=true takes the person out of every other group and resets their individual roles (a full move into this group).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "app_id": "<app_id>",
      "user_group_id": "<user_group_id>",
      "email": "<email>"
    },
    "name": "add_user_to_team_group"
  }
}

Input Schema

Name	Required	Description
`email`	Yes	User email address
`app_id`	Yes	Project ID (from list_projects)
`send_email`	No	Mail the invitation letter to a NEW account (default true). false: nobody is told a password — the person sets their own from the sign-in page.
`user_group_id`	Yes	Group ID (from list_team_groups or create_team_group)
`move_from_other_groups`	No	Remove the user from all other groups and reset their individual roles (default false)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 26, 2026

changedInput schema / properties / move_from_other_groups / description

Previous value: -"Видалити юзера з усіх інших груп і скинути індивідуальні ролі (default false)"New value: +"Remove the user from all other groups and reset their individual roles (default false)"

changedInput schema / properties / user_group_id / description

Previous value: -"ID групи (з list_team_groups або create_team_group)"New value: +"Group ID (from list_team_groups or create_team_group)"

Changed1 schema field changedOct 8, 2026

changedInput schema / properties / send_email / description

Previous value: -"Відправити email запрошення (default true)"New value: +"Mail the invitation letter to a NEW account (default true). false: nobody is told a password — the person sets their own from the sign-in page."

First observedJun 27, 2026

TDQS

B3.2/5.0

Behavior1/5

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

The description discloses useful behavior beyond the schema: account creation, invitation letter with one-time link, password visibility, and the `invitation` response field. But it also says move_from_other_groups=true removes the person from every other group and resets individual roles, which contradicts the annotation destructiveHint=false. Under the scoring rule, this contradiction forces a 1.

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

Conciseness5/5

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

The description is front-loaded with the core action and then covers account creation, invitation behavior, and the move flag without filler. The password warning is short and relevant, and every sentence contributes operational context.

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?

For a mutation tool with no output schema, it covers the key behaviors: account creation, invitation email, password handling, and the destructive effect of move_from_other_groups. It mentions the `invitation` field but omits permission requirements and error cases, leaving a small completeness gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all five parameters are already documented. The description reinforces send_email and move_from_other_groups semantics and adds the `invitation` result detail, but it does not add much beyond the schema for parameters like app_id and user_group_id. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: add a person to a team group by email. It also explains the account-creation case, making the operation concrete. It does not explicitly distinguish this from sibling tools such as add_user_to_portal_group or remove_user_from_team_group.

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

Usage Guidelines3/5

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

It explains the practical effects of send_email and move_from_other_groups, and includes a security warning about passwords. However, it does not explicitly say when to use this tool versus add_user_to_portal_group, remove_user_from_team_group, or other group-management siblings.

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

All QuintaDB 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?