Skip to main content
Glama

Coline

Change a member's role

update_member_role
DestructiveIdempotent

Changes a member's role (admin, member or guest; owner only by an owner). Only when the person asks for it.

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>",
      "workspaceMemberId": "<workspaceMemberId>",
      "role": "<role>"
    },
    "name": "update_member_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYesnull: no built-in role, only the custom roles they have.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
workspaceMemberIdYesworkspaceMemberId from list_members.

Output Schema

NameRequiredDescriptionDefault
roleYes
workspaceMemberIdYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds a permission rule not present in the structured data — that assigning the owner role requires the caller to be an owner — which is exactly the kind of authorization context that would otherwise be discovered only by failing.

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?

Two short clauses with zero filler, and the permission constraint is packed into the first sentence alongside the core purpose. Nothing could be removed without losing information.

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?

The tool is simple, has full schema coverage, and an output schema exists, so return values need not be explained. The description covers purpose, authorization, and a usage guard; the only meaningful gap is that it never clarifies workspace-member scope versus the team/channel role tools that share near-identical names.

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%: workspace slug, workspaceMemberId provenance, and the role enum are all documented in the schema itself. The description's role list duplicates the enum rather than adding constraints or format detail, so it neither compensates for nor improves on the schema.

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 opens with a specific verb and resource ("Changes a member's role") and enumerates the accepted role values, so the operation is unambiguous. It does not distinguish itself from similarly named siblings such as update_team_member_role or set_channel_role, so an agent must infer scope from the parameter names rather than the prose.

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?

"Only when the person asks for it" is a real usage constraint that tells the agent not to act proactively, which is more than nothing. However, it gives no positive context about when a role change is appropriate and never names an alternative tool for team-level or channel-level role changes.

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