Skip to main content
Glama

Кого оставить с местом

set_workspace_seats
Destructive

Когда участников больше, чем мест в тарифе, выбирает, кто останется с местом; остальные без места через 14 дней теряют доступ (или теряют сразу, если срок уже прошёл). Сколько мест и кто без места — seats в get_workspace_tariff и seat_until в get_workspace_members. Владельца передавать не нужно — его место есть всегда. Выбор заменяет прежний целиком; когда мест снова хватает, он забывается. Лучший выход — улучшить тариф: seats.offer — какой тариф и сколько стоит. Нужно право «Участники».

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_ids": "<member_ids>"
    },
    "name": "set_workspace_seats"
  }
}

Input Schema

NameRequiredDescriptionDefault
member_idsYesmember_id из get_workspace_members — кого оставить с местом. Не больше, чем мест в тарифе минус одно (владельца). Пустой список — никого не отмечать.
workspace_idYesID воркспейса (из workspace://list).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description goes well beyond them: the 14-day grace window, immediate loss when the deadline has passed, and full replacement of the prior selection rather than a merge. It stops short of saying whether re-invoking resets the 14-day timer, which matters given idempotentHint=false and the replace-wholesale semantics.

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 situation and consequence, then inputs, then the recommended alternative, then the permission — a logical order with no filler. The semicolon-and-dash chaining makes it dense and slightly hard to scan, but every sentence carries information an agent needs.

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 destructive two-parameter mutation with no output schema, it covers the timing of the effect, the replacement semantics, the owner exemption, the permission requirement, and the preferred alternative. An agent can call this correctly without consulting other documentation.

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 schema already documents the member_ids cap (seats minus one, owner excluded) and the empty-list meaning, so the description mostly restates rather than adds. Its only genuine additions are the cross-references to get_workspace_tariff and get_workspace_members for deriving seats and member ids.

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?

Names a specific action on a specific resource (choosing which members keep a plan seat when members outnumber seats) and immediately states the consequence: the rest lose access in 14 days or at once if the deadline passed. It is clearly distinguishable from sibling tools like set_workspace_member_role or set_workspace_member_blocked, which operate on a single member.

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 tells the agent where to get the inputs (seats in get_workspace_tariff, seat_until in get_workspace_members), states a prerequisite permission («Участники»), and routes to the preferred alternative — upgrading the plan via seats.offer — rather than manually dropping people. It also states the owner must not be passed, removing a common mis-invocation.

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