Skip to main content
Glama

Папки, доступные участнику

set_workspace_member_folders
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>",
      "folder_ids": "<folder_ids>"
    },
    "name": "set_workspace_member_folders"
  }
}

Input Schema

NameRequiredDescriptionDefault
member_idYesID участника (member_id из get_workspace_members).
folder_idsYesID папок целиком, прежний список заменяется. Пустой список означает доступ ко всем папкам аккаунта — они будут назначены поимённо.
workspace_idYesID воркспейса (из workspace://list).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only flag destructiveHint=true generically; the description concretely explains what is destroyed – the previous folder list is fully replaced, and passing three folders leaves the member with exactly those. It also discloses the non-obvious empty-list behavior that grants access to all account folders. Minor tension: full-replacement semantics read as idempotent, while idempotentHint=false, but the destructive explanation itself is consistent with the annotations.

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, then the replacement rule, then the empty-list edge case. Nothing is redundant and the concrete 'three folders' example makes the semantics immediate.

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 three-parameter mutation tool with full schema documentation and no output schema, the description covers the critical behavioral facts: replacement of prior state and empty-list meaning. It omits authorization requirements and what happens with invalid or inaccessible folder IDs, which leaves a small but real gap.

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 the folder_ids parameter description already states that the whole list is replaced and that an empty list grants access to all folders. The description's 'открывает все папки аккаунта' largely restates this, adding no format, limits, or error details 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb plus resource ('Задаёт, какие папки видит участник' – sets which folders a member sees), so the effect is unambiguous. It does not explicitly distinguish itself from nearby siblings such as manage_workspace_folder or set_workspace_member_api_access, which is the only thing keeping it below a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use or when-not guidance and no mention of alternatives or preconditions (admin rights, effect on other access settings). An agent must infer from the name alone whether this is the right tool versus manage_workspace_folder or the other set_workspace_member_* setters.

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