Skip to main content
Glama

Add people to a Role

add_role_members
DestructiveIdempotent

Add people to one Role. user_ids are the ids list_users reports; invitations are included, and they hold the Role immediately. Each id is reported as added, already_member, refused, or outcome_unknown with a code. Adding a person to the Administrator Role replaces their custom Roles and keeps Member; everyone else keeps the Roles they already hold. Change at most 25 people's tiers per call. For outcome_unknown, repeat the same edit as the per-person message explains.

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": {
      "role_id": "<role_id>",
      "user_ids": "<user_ids>"
    },
    "name": "add_role_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
role_idYesUUID of the Role
user_idsYesThe ids list_users reports, for members and invitations

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already flag destructive=true and idempotent=true; the description adds substantial behavior beyond them: per-id outcome codes (added, already_member, refused, outcome_unknown), the Administrator Role replacement rule (custom Roles replaced, Member kept), and the 25-per-call limit. This is exactly the mutation detail an agent needs before calling.

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?

Five sentences, each carrying distinct information, with the core action front-loaded. Slightly dense with outcome-code detail, but nothing is wasted and the Administrator Role caveat earns its place.

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 two-parameter mutation with no output schema, the description covers outcomes, side effects, and rate limits well. It could say more about what 'refused' means or whether partial success is possible, but an agent can call it correctly from this.

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 coverage is 100%, so role_id and user_ids are already documented. The description reinforces that user_ids are the ids list_users reports and that invitations count, adding some meaning, but does not explain id formats or what a refused code means for the caller.

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 opens with a specific verb+resource ('Add people to one Role') and immediately disambiguates scope: one Role, not many. It is clearly distinct from siblings like remove_role_members and invite_users, and it clarifies that invitations are included.

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?

It states when ids are valid (the ids list_users reports) and gives a clear retry instruction for outcome_unknown, plus the constraint of at most 25 people per call. It does not explicitly contrast with remove_role_members or invite_users, but the usage context is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources