Skip to main content
Glama

Change workspace member access

update_workspace_member
DestructiveIdempotent

Changes a non-owner member’s role or removes their workspace access. Existing workspace projects remain in place.

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>",
      "user_id": "<user_id>",
      "role": "<role>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "update_workspace_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYes
user_idYes
workspace_idYesExact workspace ID from list_workspaces. Never infer a workspace from a project name.
idempotency_keyYesUnique write key. Reuse the same key and input after an uncertain response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, so the description is not required to restate safety. It still adds real context: the target must be a non-owner, and role changes/removal leave existing workspace projects intact — a non-obvious consequence for a destructive operation. It omits whether removal is reversible or what happens to the removed member's project access.

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 sentences, no waste, with the core action stated first and the project-persistence caveat second. Every sentence carries information an agent would otherwise have to guess.

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 small 4-parameter mutation tool with no output schema and annotations covering safety and idempotency, this covers the essentials, including the owner restriction and the side-effect scope. Missing only caller-permission requirements and the reversibility of removal.

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 50%, and the workspace_id and idempotency_key descriptions are already in the schema. The description clarifies that the role parameter has two modes (assign a role or remove access), which maps to the 'remove' enum value, but adds no detail on user_id or when to use which enum. 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?

States a specific verb+resource: changes a member's role or removes workspace access. The 'non-owner' qualifier and the dual mode (role change vs. removal) make it distinguishable from invite_workspace_member, though it never names the sibling. Clear enough an agent knows what it does 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 Guidelines3/5

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

Implies the use case: only for existing non-owner members who need a role change or removal. It does not say when NOT to use it or point to invite_workspace_member for adding members, nor does it state prerequisites such as caller permissions. Adequate but leaves routing to inference.

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