Skip to main content
Glama

Исключение участника

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

Input Schema

NameRequiredDescriptionDefault
member_idYesID участника (member_id из get_workspace_members).
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?

Beyond the annotations (destructiveHint=true, idempotentHint=false), the description discloses exactly what is destroyed — access plus folder bindings — what survives (surveys the member created), and the cost of reversal (new invitation plus manual folder reassignment). This is the precise information an agent needs before an irreversible write.

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, each carrying a distinct fact: what is lost, what is kept, what reversal costs. The most important consequence (immediate access loss) is front-loaded and there is no filler.

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

Completeness5/5

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

For a two-parameter destructive mutation with no output schema, the description covers effect scope, collateral effects, data retention, and reversibility — everything needed to call it responsibly. No relevant gap remains.

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% and both parameters already point at their source (get_workspace_members, workspace://list), so the schema carries parameter meaning. The description adds nothing about parameters, which is acceptable at full coverage but not above baseline.

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 states a specific verb and resource — removing a member from the account — and scopes it by noting that folder assignments go with them. It does not explicitly contrast with the nearby set_workspace_member_blocked, so an agent must infer the distinction from the consequences described rather than from a named alternative.

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?

Usage is implied rather than stated: the permanence ('return only via a new invitation') signals this is a hard removal, implicitly steering an agent away from a temporary block. There is no explicit when-to-use/when-not-to-use statement or named sibling, leaving the comparison to inference.

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