Skip to main content
Glama

Доступы участника

get_workspace_member_access
Read-onlyIdempotent

Возвращает права одного участника — те же, по которым отказывает система. Отвечает на вопрос «почему коллега не видит ответы или не может удалить опрос». Показывает роль, доступные папки, отличия прав в отдельных папках (folder_access — в этих папках действуют они, в остальных общий набор), откуда взяты права (из роли или из значений по умолчанию) и поле blocked — причину, по которой участник не работает независимо от прав: invite_not_accepted (не перешёл по приглашению) или email_not_confirmed (не подтвердил почту).

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

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.4/5.0
Behavior5/5

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

Annotations already cover the read-only, idempotent, non-destructive profile, and the description goes well beyond them. It enumerates the response contents (role, accessible folders, per-folder overrides, provenance of rights) and explains the blocked field with its two enum values, which no annotation or schema field conveys.

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?

Front-loaded with the core purpose, then progressively deeper detail, with no filler sentences. It is a single dense paragraph with nested parentheticals, which makes it slightly harder to scan than it could be.

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?

There is no output schema, so the description must carry the return-value burden, and it does: it names the role, folder list, per-folder differences, rights provenance, and the blocked reason semantics. For a two-parameter read tool, an agent has everything needed to call and interpret it.

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 already document their origin (member_id from get_workspace_members, workspace_id from workspace://list). The description adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 scopes it to a single member, which cleanly separates it from list-oriented siblings like get_workspace_members. The added framing "те же, по которым отказывает система" tells the agent exactly what kind of data this is.

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?

Gives a concrete triggering scenario: diagnosing why a colleague cannot see responses or delete a quiz. That is real when-to-use guidance, but there is no explicit exclusion or named alternative (e.g., when to use get_workspace_roles instead), so it stops short of a 5.

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