Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

workspace_member_update

Change a member's role in the active workspace (or one named by workspace_id). Requires owner or admin role. Name the person by email, username or numeric user id — workspace.members lists them. Promoting to 'admin' also grants member management; ownership is moved separately and cannot be set here.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roleYesNew role for this member.
memberYesWho to change: a member's email, username, or numeric user id. Call workspace.members to see who is in the workspace.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
workspace_idNoNumeric workspace id. Omit to target the currently-routed workspace (workspace.current).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
+  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
+  "type": "integer"
+}
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), but the description adds real context beyond them: the owner/admin authorization requirement and the side effect that promoting to 'admin' grants member management. It does not say whether a change can be reverted or what happens on failure, so it falls just short of the top.

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 sentences, each load-bearing: action, precondition plus identification, then the role-semantics caveat. The core action is front-loaded and no sentence is filler.

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 mutation tool with no output schema, the description covers the important ground: authorization, who to target, how to find members, and what promotion does and does not grant. Only minor gaps remain (reversibility, error behavior) that an agent could infer.

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%, so role, member, in_workspace, and workspace_id are all already documented in the schema. The description restates the member identification formats and the workspace_id targeting, adding little new semantics, and never addresses the in_workspace override. Baseline 3 applies when the schema carries the load.

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 ('Change a member's role') plus the scope of the target workspace. It is immediately distinguishable from siblings like workspace_member_remove, workspace_invite, and workspace_members without opening any 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?

Gives the precondition ('Requires owner or admin role'), the identification options for the member, and a pointer to workspace.members for discovery. It also states an explicit exclusion — ownership is moved separately and cannot be set here — which is exactly the when-not guidance an agent needs.

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

All dialogbrain 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