Skip to main content
Glama

Coline

Change a team role

update_team_member_role
DestructiveIdempotent

Changes someone's role in a team (owner, admin or member).

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": {
      "workspace": "<workspace>",
      "teamId": "<teamId>",
      "userId": "<userId>",
      "role": "<role>"
    },
    "name": "update_team_member_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYes
teamIdYesTeam id from list_teams.
userIdYesThe person's user id (userId from list_members).
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
memberYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds nothing beyond that: it never mentions that the change alters permissions, who is authorized to make it, whether an owner can demote themselves or the last owner, or what side effects follow. The role list it does include merely repeats the schema enum.

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?

A single, front-loaded sentence with no filler. It is terse to the point of omission, but nothing written is wasted.

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

Completeness2/5

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

For a destructive permission-mutating tool with four required parameters, the description omits critical context: required authorization level, safeguards around owner demotion, and confirmation of what changes. Output values need not be explained because an output schema exists, but the operational gaps remain significant.

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 75% and the schema itself explains where teamId, userId and workspace come from, so the baseline is 3. The description's only parameter-related content is the parenthetical role list, which duplicates the enum in the schema without adding meaning.

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?

States a specific verb and resource ("Changes someone's role in a team") and enumerates the allowed roles, so the basic action is unambiguous. It does not differentiate itself from the very similar sibling update_member_role, leaving the agent to guess whether the scope is team-level or workspace-level.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as update_member_role, add_team_member, or remove_team_member. The agent must infer from the name alone that this targets an existing team member rather than adding or removing one.

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