Skip to main content
Glama

add_workspace_member

Adds an existing organization user to a workspace and assigns a role; use it to grant workspace access by user UUID.

Instructions

Add an existing org user to a workspace with a role. Requires a UUID user_id; use list_all_users to find it, and invite_user first if the person is not yet in the org.

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>"
    },
    "name": "add_workspace_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYesRole in the workspace
user_idYesThe user ID to add (must be a valid UUID from list_all_users, not an email address)
workspace_idYesThe workspace ID to add the member to

Output Schema

NameRequiredDescriptionDefault
okYesCall succeeded
dataNoSuccess payload
errorNoFailure details

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.16.5
    • changedOutput schema / properties / data / description
      Previous value: -"Structured success payload when ok is true"New value: +"Success payload"
    • changedOutput schema / properties / error / description
      Previous value: -"Structured error payload when ok is false"New value: +"Failure details"
    • changedOutput schema / properties / error / properties / details / description
      Previous value: -"Optional structured error details"New value: +"Extra error details"
    • changedOutput schema / properties / error / properties / message / description
      Previous value: -"Human-readable error message"New value: +"Error message"
    • changedOutput schema / properties / ok / description
      Previous value: -"Whether the tool call succeeded and returned structured data"New value: +"Call succeeded"
  2. Changed1 schema field changedv1.0.11
    • addedInput schema / properties / workspace_id / minLength
      Added value: +1
  3. Changed2 schema fields changedv1.0.9
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  4. Addedv1.0.1
  5. Removed
  6. First observed

TDQS

A4.2/5.0
Behavior3/5

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

The annotations already declare the mutation and safety profile (readOnly=false, destructive=false, idempotent=false, openWorld=true). The description adds real value by stating the precondition that the user must already exist in the org and the resolution step for the identifier. However, it does not explain the non-idempotent behavior — what happens if the user is already a member (error, silent no-op, role overwrite) — nor the effect of granting admin vs member, which is the main behavioral risk here.

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 tight sentences with the core action first and the prerequisites immediately after; every clause carries operational information and nothing is padded.

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?

With only three required parameters, a full output schema, and complete annotations, the description covers the action, the identifier resolution path, and the org-membership prerequisite. The remaining gap is the duplicate-add / non-idempotent case and permission requirements, which an agent would likely want before calling.

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 100%: workspace_id, user_id (with UUID pattern and an explicit 'not an email address' note), and role (enum of admin/member/manager) are all documented in the schema. The description restates the UUID requirement and adds the resolution pointer to list_all_users, which is mildly useful routing but largely duplicates schema text; it says nothing about what the role choices entitle the user to.

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?

The description states a specific verb and resource ("Add ... to a workspace with a role") and narrows the scope with "existing org user", which cleanly separates it from invite_user (which brings a non-org person in) and from update_workspace_member (which changes a role). An agent can pick this tool without opening a schema.

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

Usage Guidelines5/5

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

It gives an explicit prerequisite chain: the person must already be in the org, use list_all_users to resolve the user_id, and call invite_user first if they are not. That is when-to-use, when-not-to-use, and a named alternative all in one sentence.

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

Deploy Server

Other Tools