Skip to main content
Glama

Change a member's role

set_member_role
Destructive

Set a membership's role to member or admin. Cannot demote an owner; transfer ownership instead. Workspace owners only.

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_id": "<workspace_id>",
      "membership_id": "<membership_id>",
      "role": "<role>"
    },
    "name": "set_member_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYes
workspace_idYesThe workspace id (from whoami).
membership_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the mutation profile is known. The description adds genuinely new behavioral context: the authorization requirement (caller must be a workspace owner) and the hard business rule that owners cannot be demoted, with the routing to transfer_ownership. It stops short of saying the previous role is overwritten or what happens on partial failure.

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?

Three short sentences, zero filler, and the primary action is front-loaded before constraints. Every clause carries distinct information (action, restriction, authorization).

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 3-parameter mutation tool with annotations covering the destructive profile and no output schema, the description covers the key risks: permission gating, the owner-demotion rule, and the correct alternative. The one real gap is the provenance of membership_id, which an agent needs in order to call the tool successfully.

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

Parameters2/5

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

Schema coverage is only 33%: workspace_id is documented ('from whoami'), role is an enum that speaks for itself, but membership_id has no description anywhere. The description restates the role enum ('member or admin') rather than explaining how to obtain a membership_id (e.g., via list_members), so it does not compensate for the coverage gap.

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 ('Set a membership's role') plus the exact valid targets ('member or admin'), which lets an agent distinguish it from remove_member, invite_member, and transfer_ownership without opening the schema.

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?

Gives a clear exclusion with a named alternative ('Cannot demote an owner; transfer ownership instead') and a prerequisite ('Workspace owners only'). It does not state the converse case (removing a member should use remove_member), but the when-not guidance it does give is explicit.

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