Skip to main content
Glama

Удаление роли участника

delete_workspace_role
Destructive

Удаляет роль аккаунта. Участники этой роли переводятся на роль по умолчанию, то есть их возможности меняются. Встроенные роли удалить нельзя.

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

Input Schema

NameRequiredDescriptionDefault
role_idYesID роли (из get_workspace_roles).
workspace_idYesID воркспейса (из workspace://list).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered; the description goes further and discloses the cascade effect that members of the deleted role are moved to the default role and lose capabilities. That side effect is not derivable from the schema or annotations and is exactly the context an agent needs before a destructive call.

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 short sentences, front-loaded with the action and its side effect, followed by the hard precondition. Nothing is padding and the most safety-relevant fact is not buried.

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 two-parameter destructive tool with full annotation and schema coverage, the description covers action, cascade consequence, and eligibility constraint. It stops short of saying what the call returns or how failure on a built-in role is signalled, a minor gap given no output schema exists.

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 both parameters carry descriptions pointing at their source (role_id from get_workspace_roles, workspace_id from workspace://list). The description adds no further parameter meaning, which is acceptable at this coverage level.

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 ("Удаляет роль аккаунта" – deletes an account role) and adds the scope constraint that built-in roles are excluded, which sharpens the boundary. It does not explicitly contrast itself with save_workspace_role or set_workspace_member_role, so the sibling 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 Guidelines4/5

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

It gives a concrete when-not condition ("Встроенные роли удалить нельзя"), which prevents a failed call and is a real usage rule. It does not point to an alternative tool for the cases where deletion is inappropriate, e.g. reassigning members instead.

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