Skip to main content
Glama

Участники аккаунта

get_workspace_members
Read-onlyIdempotent

Возвращает состав аккаунта: участники, их роли, принято ли приглашение, доступные папки и последняя активность. Сам инструмент только читает; пригласить — invite_workspace_member, сменить роль — set_workspace_member_role, папки — set_workspace_member_folders, доступ к API — set_workspace_member_api_access, исключить — remove_workspace_member, повторить приглашение — resend_workspace_member_invite, закрыть или вернуть доступ — set_workspace_member_blocked (blocked_at в строке: когда доступ закрыт, null — открыт; blocked_reason: owner — закрыл владелец, seats — не хватило мест в тарифе), кого оставить с местом при нехватке — set_workspace_seats (seat_until: последний день доступа у того, кто без места; invite_expires_at: когда истечёт неотвеченное приглашение — оно живёт 7 дней). Нужен, когда надо понять, кто работает в аккаунте и почему у коллеги нет доступа.

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": "get_workspace_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoСколько участников вернуть, по умолчанию 100, максимум 500.
offsetNoСколько участников пропустить, по умолчанию 0.
statusNoКого показать: all — всех (по умолчанию), active — только принявших приглашение, pending — только приглашённых.
workspace_idYesID воркспейса (из workspace://list).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint, and the description reinforces this with 'Сам инструмент только читает'. Beyond that it explains row-level semantics that no structured field carries: blocked_at null vs set, blocked_reason owner vs seats, seat_until and the 7-day invite_expires_at lifetime. It stops short of describing pagination or response ordering, which keeps it off a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded and nothing is filler, but the sibling routing list and the parenthetical field glosses are packed into one very long run-on sentence, making it dense to scan. A bulleted or sentence-per-group layout would preserve the same content with far better structure.

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?

There is no output schema, so the description correctly compensates by naming the fields returned and decoding the non-obvious ones (blocked_at, blocked_reason, seat_until, invite_expires_at). With all four parameters documented in the schema and safety covered by annotations, the only remaining gap is pagination/ordering behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with an enum and min/max bounds, so the schema already carries the parameter burden and the baseline is 3. The description goes slightly beyond by defining the meaning of the returned status-related fields an agent will read after calling, which helps interpret limit/offset/status results in context.

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 ('Возвращает состав аккаунта') and then enumerates exactly what comes back: members, roles, invitation acceptance, folders, last activity. It is clearly distinguishable from the mutation siblings it names, so an agent can tell read from write without opening a 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?

Explicitly routes each adjacent action to its own tool (invite_workspace_member, set_workspace_member_role, set_workspace_member_folders, remove_workspace_member, set_workspace_member_blocked, set_workspace_seats, and more), and closes with the concrete situation that selects this tool ('кто работает в аккаунте и почему у коллеги нет доступа'). Both when-to-use and when-not-to-use are present.

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