Skip to main content
Glama
Sign In

Tokenrip

by com.tokenrip
OverviewDiscussionsAdmin

Set workspace member role

workspace_member_set_role
DestructiveIdempotent

Change a member's role: editor (reads, writes and shares everything) or viewer (reads everything). member is the row id from workspace_member_list (it stands alone), or an account id, alias or email address with workspaceId. Anyone who may share here (editors, guests included). A change to viewer immediately releases the member's task holds and browser views.

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": {
      "member": "<member>",
      "role": "<role>"
    },
    "name": "workspace_member_set_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
whyNoRequired for workspace items: one sentence on what the person is trying to accomplish, in their terms, not a description of this edit. Every workspace write takes one; sessions and summaries record themselves from it. At most 300 characters.
roleYesviewer or editor.
memberYesThe member: its row id (id from the member list; it stands alone), or an account id, alias or email address with workspaceId (the person's primary-account row, or the row an add or invite by the address made).
workspaceIdNoThe workspace (its id or its slug), when member is an account id, alias or email; optional beside a row id (the row must be in it).

Output Schema

NameRequiredDescriptionDefault
memberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / membership
      Removed value: -{
-  "description": "external only: a person added to a workspace is a guest (shared items only); internal access comes from owning the workspace or being in its team, so internal is refused INTERNAL_NEEDS_TEAM. external changes nothing.",
-  "enum": [
-    "internal",
-    "external"
-  ],
-  "type": "string"
-}
    • changedInput schema / properties / role / description
      Previous value: -"viewer or editor; kept when omitted."New value: +"viewer or editor."
    • changedInput schema / required
      Previous value: -[
-  "member"
-]New value: +[
+  "member",
+  "role"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / membership / description
      Previous value: -"internal or external; kept when omitted."New value: +"external only: a person added to a workspace is a guest (shared items only); internal access comes from owning the workspace or being in its team, so internal is refused INTERNAL_NEEDS_TEAM. external changes nothing."
  3. Changed5 schema fields changed
    • changedInput schema / properties / workspaceId / description
      Previous value: -"The workspace, when member is an account id, alias or email; optional beside a row id (the row must be in it)."New value: +"The workspace (its id or its slug), when member is an account id, alias or email; optional beside a row id (the row must be in it)."
    • removedInput schema / properties / workspaceId / format
      Removed value: -"uuid"
    • addedInput schema / properties / workspaceId / maxLength
      Added value: +64
    • addedInput schema / properties / workspaceId / minLength
      Added value: +1
    • removedInput schema / properties / workspaceId / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  4. First observed

TDQS

A4/5.0
Behavior5/5

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

The description adds substantial behavior beyond the annotations: demoting to viewer 'immediately releases the member's task holds and browser views', which is a concrete side effect the agent could not derive from destructiveHint alone. It also states the authorization requirement ('Anyone who may share here'), covering both impact and access preconditions.

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?

Three front-loaded sentences: effect and role semantics first, then how to identify the member, then the side effect. Dense and largely waste-free, though the parenthetical 'it stands alone' repeats a phrase already used in the schema and adds little.

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 destructive mutation with full schema coverage and an output schema, the description covers the essential unknowns: role meaning, identifier sourcing, permissions, and the task-hold/browser-view side effect. The only omission is any reference to the required 'why' rationale parameter, which the agent must discover from the schema.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, and the description exceeds it by explaining what editor and viewer actually grant (reads, writes and shares everything vs reads everything) rather than just repeating the enum labels. The member/workspaceId resolution text largely duplicates the schema, and the required 'why' parameter is never mentioned in the description.

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 (change a member's role) and enumerates the two possible values with their meaning, so the agent knows exactly what the tool does. It does not explicitly contrast itself with the sibling team_set_member_role, so the workspace scope must be inferred from the name and the workspaceId parameter.

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?

Permission context is given ('Anyone who may share here (editors, guests included)') and it points at workspace_member_list as the source of the row id, which helps the agent call it correctly. But there is no explicit when-to-use versus workspace_member_add / workspace_member_remove / team_set_member_role, and no statement about when not to use it.

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

All Tokenrip toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources