Skip to main content
Glama

Роль участника

save_workspace_role
Destructive

Создаёт роль или меняет права существующей. Правка действует сразу на всех участников этой роли. Значения прав: allowed — разрешено, partially — только свои объекты, forbidden — запрещено. Без role_id создаётся новая роль, с role_id — правится указанная. Настройка ролей доступна не на всех тарифах.

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

Input Schema

NameRequiredDescriptionDefault
nameYesНазвание роли.
role_idNoID роли для правки (из get_workspace_roles). Не передавайте, чтобы создать новую.
permissionsYesПолный набор прав роли. Имена прав берите из get_workspace_roles.
workspace_idYesID воркспейса (из workspace://list).
folder_permissionsNoОтличия прав роли в отдельных папках: список записей {folder_id, permissions}. Не передавайте, чтобы оставить отличия как есть; пустой массив снимает все, и роль везде работает по базовым правам.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, but the description adds material context beyond them: edits take effect immediately for every member holding that role, and role configuration is gated by tariff. Both are operationally important for a mutation tool. It does not say what happens to permissions omitted from the payload or whether a failed call leaves partial state, so it is not fully transparent.

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?

Four short sentences, front-loaded with the create/edit duality and the blast radius, then the value vocabulary and the tariff caveat. Nothing is padded. Minor redundancy: the permission value glossary duplicates what the schema already states verbatim.

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, non-idempotent mutation with no output schema, the description covers the essentials an agent needs: create-vs-edit switch, immediate workspace-wide effect, value vocabulary, and availability constraints. Gaps remain around failure modes and whether the permissions list is a full replacement set (that detail lives only in the schema), but nothing critical is missing.

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 the schema already carries parameter meaning; the baseline of 3 applies. The description restates the allowed/partially/forbidden value semantics and the role_id create-vs-edit behavior, both of which already appear in the schema, so it adds little new meaning. The nuanced folder_permissions reset behavior is documented only in the schema, not reinforced 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?

The description names a specific resource (роль) and both verbs it supports: creating a role and changing the permissions of an existing one. The role_id clause makes the create-vs-edit split explicit. It stops short of distinguishing itself from related siblings such as set_workspace_member_role (assigning a role to a member) or delete_workspace_role, so an agent must infer that boundary.

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 usable routing logic — omit role_id to create, pass role_id to edit — plus a tariff caveat ('доступна не на всех тарифах'). However, it never names an alternative tool or states when this should not be used (e.g., assigning roles to members, deleting roles), leaving the agent to infer sibling boundaries on its own.

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