Skip to main content
Glama

Доступ участников к папке

manage_folder_access
Destructive

Доступ к папке со стороны самой папки: показывает, у кого он есть, и выдаёт или снимает его одному человеку. Доступ участника к опросам держится на привязке к папкам. Соседний set_workspace_member_folders смотрит с другой стороны — перезаписывает весь список папок одного участника целиком, поэтому для точечной правки годится этот инструмент. Признак active в списке говорит, принял ли человек приглашение: пока нет, доступ выдан, но им никто не пользуется.

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>",
      "folder_id": "<folder_id>",
      "action": "<action>"
    },
    "name": "manage_folder_access"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesЧто сделать: members — кто имеет доступ, add — выдать доступ, remove — снять.
folder_idYesID папки (folder://list).
member_idNoID участника из get_workspace_members. Нужен для add и remove.
workspace_idYesID workspace. Взять из 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 destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is covered. The description adds context the annotations cannot: that access is per-one-person, that folder bindings underpin quiz access, and that an 'active' entry means the invitation is unaccepted so granted access is effectively unused. It stops short of saying what happens to dependent quiz access when remove is applied.

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?

Four short sentences with the core verb set front-loaded, then the dependency context, then the sibling disambiguation, then the caveat about unaccepted invitations. Every sentence carries information the agent would otherwise have to guess.

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 three-action mutation with full annotation coverage and no output schema, the description covers scope, alternative, and the one non-obvious return flag. The only gap is the downstream effect of remove on members whose quiz access depends on the folder.

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 the action enum is already documented in the schema, so the description has little left to add about parameters. It explains the meaning of the 'active' result marker instead, which is useful but belongs to output semantics rather than parameter guidance. Baseline 3 is appropriate.

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?

The description names a specific verb set and resource — showing, granting and revoking folder access for a single member ('показывает, у кого он есть, и выдаёт или снимает его одному человеку'). It also explicitly contrasts scope with the sibling set_workspace_member_folders, so the tool can be distinguished without opening either 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?

It states exactly when this tool is the right choice: for a point edit of one person's access, whereas set_workspace_member_folders rewrites a member's entire folder list. That is an explicit alternative-plus-condition, not vague implied usage.

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