Skip to main content
Glama

Смена роли участника

set_workspace_member_role
Destructive

Меняет роль участника — то есть то, что он может делать в аккаунте. Действует сразу. Роль берётся из этого же аккаунта (из get_workspace_roles).

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>",
      "member_id": "<member_id>",
      "role_id": "<role_id>"
    },
    "name": "set_workspace_member_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
role_idYesID новой роли (из get_workspace_roles).
member_idYesID участника (member_id из get_workspace_members).
workspace_idYesID воркспейса (из workspace://list).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

"Действует сразу" adds real context beyond the annotations: the change takes effect immediately with no confirmation step. However, despite destructiveHint=true, the description never warns that lowering a role revokes existing capabilities or that the change is not idempotent, so the destructive consequence is left implied.

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 short sentences with the action stated first, then the effect, then the role source. The explanatory clause on what a role means earns its place; little is wasted, though the sentence order could put the immediacy caveat more prominently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter mutation with no output schema, the description covers the action, immediacy, and role provenance. It stops short of describing what happens to existing access on a downgrade or what the call returns, which matters given the destructive annotation.

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% and every parameter already documents its source (get_workspace_roles, get_workspace_members, workspace://list). The description only repeats the role-source hint, adding no new meaning about formats or constraints, so the baseline 3 applies.

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?

The description names a specific verb and resource ("Меняет роль участника") and clarifies what a role means ("то, что он может делать в аккаунте"), which partially separates it from sibling setters like set_workspace_member_api_access or set_workspace_member_blocked. It never names those siblings explicitly, so the differentiation is inferred rather than stated.

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?

It gives a precondition hint by pointing to get_workspace_roles as the source of the role, but it does not say when to prefer this tool over the adjacent access/blocked/folders setters. The guidance is implied rather than 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