Skip to main content
Glama
uk-kd

operbots-mcp

by uk-kd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Добавить участника или изменить его права

members_save

Add registered people to cases by email, or edit a member's role, note, extra grants, and revoked permissions. For uninvited emails, send an invite link first.

Instructions

Без параметра member добавляет в дело уже зарегистрированного человека по почте. С параметром member меняет его роль и точечные права поверх роли. Если человек ещё не зарегистрирован, создайте ссылку-приглашение через invites_create.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
caseNoДело: название или идентификатор. Если не указать, берётся дело по умолчанию, иначе последнее открытое в панели.
noteNoСлужебная пометка об участнике. null — стереть.
roleNoРоль: название, короткое имя или идентификатор. Готовые: owner, admin, builder, operator, observer. По умолчанию при добавлении назначается «оператор». null — снять роль.
emailNoПочта того, кого добавляем в дело.
memberNoКого менять: почта, имя или идентификатор участия. Не указывайте для добавления.
extra_permissionsNoПрава поверх роли. Заменяет прежний список целиком.
revoked_permissionsNoПрава, отбираемые у участника вопреки роли. Заменяет прежний список целиком.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.2.0
    • changedInput schema / properties / extra_permissions / items / enum
      Previous value: -[
-  "case.view",
-  "case.edit",
-  "case.delete",
-  "case.transfer",
-  "member.view",
-  "member.invite",
-  "member.edit",
-  "member.remove",
-  "role.view",
-  "role.manage",
-  "bot.view",
-  "bot.create",
-  "bot.edit",
-  "bot.delete",
-  "bot.control",
-  "bot.token_reveal",
-  "flow.view",
-  "flow.edit",
-  "flow.publish",
-  "flow.delete",
-  "market.publish",
-  "chat.view",
-  "chat.reply",
-  "chat.takeover",
-  "chat.broadcast",
-  "chat.delete",
-  "ai.view",
-  "ai.manage",
-  "knowledge.view",
-  "knowledge.edit",
-  "audit.view"
-]New value: +[
+  "case.view",
+  "case.edit",
+  "case.delete",
+  "case.transfer",
+  "member.view",
+  "member.invite",
+  "member.edit",
+  "member.remove",
+  "role.view",
+  "role.manage",
+  "bot.view",
+  "bot.create",
+  "bot.edit",
+  "bot.delete",
+  "bot.control",
+  "bot.token_reveal",
+  "flow.view",
+  "flow.edit",
+  "flow.publish",
+  "flow.delete",
+  "market.publish",
+  "chat.view",
+  "chat.reply",
+  "chat.takeover",
+  "chat.broadcast",
+  "chat.delete",
+  "request.view",
+  "request.create",
+  "request.edit",
+  "request.manage",
+  "counterparty.view",
+  "counterparty.manage",
+  "ai.view",
+  "ai.manage",
+  "extension.view",
+  "extension.manage",
+  "knowledge.view",
+  "knowledge.edit",
+  "audit.view"
+]
    • addedInput schema / properties / note / anyOf
      Added value: +[
+  {
+    "maxLength": 240,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / note / description
      Previous value: -"Служебная пометка об участнике."New value: +"Служебная пометка об участнике. null — стереть."
    • removedInput schema / properties / note / maxLength
      Removed value: -240
    • removedInput schema / properties / note / type
      Removed value: -"string"
    • changedInput schema / properties / revoked_permissions / items / enum
      Previous value: -[
-  "case.view",
-  "case.edit",
-  "case.delete",
-  "case.transfer",
-  "member.view",
-  "member.invite",
-  "member.edit",
-  "member.remove",
-  "role.view",
-  "role.manage",
-  "bot.view",
-  "bot.create",
-  "bot.edit",
-  "bot.delete",
-  "bot.control",
-  "bot.token_reveal",
-  "flow.view",
-  "flow.edit",
-  "flow.publish",
-  "flow.delete",
-  "market.publish",
-  "chat.view",
-  "chat.reply",
-  "chat.takeover",
-  "chat.broadcast",
-  "chat.delete",
-  "ai.view",
-  "ai.manage",
-  "knowledge.view",
-  "knowledge.edit",
-  "audit.view"
-]New value: +[
+  "case.view",
+  "case.edit",
+  "case.delete",
+  "case.transfer",
+  "member.view",
+  "member.invite",
+  "member.edit",
+  "member.remove",
+  "role.view",
+  "role.manage",
+  "bot.view",
+  "bot.create",
+  "bot.edit",
+  "bot.delete",
+  "bot.control",
+  "bot.token_reveal",
+  "flow.view",
+  "flow.edit",
+  "flow.publish",
+  "flow.delete",
+  "market.publish",
+  "chat.view",
+  "chat.reply",
+  "chat.takeover",
+  "chat.broadcast",
+  "chat.delete",
+  "request.view",
+  "request.create",
+  "request.edit",
+  "request.manage",
+  "counterparty.view",
+  "counterparty.manage",
+  "ai.view",
+  "ai.manage",
+  "extension.view",
+  "extension.manage",
+  "knowledge.view",
+  "knowledge.edit",
+  "audit.view"
+]
    • changedInput schema / properties / role / description
      Previous value: -"Роль: название, короткое имя или идентификатор. Готовые: owner, admin, builder, operator, observer. По умолчанию при добавлении назначается «оператор»."New value: +"Роль: название, короткое имя или идентификатор. Готовые: owner, admin, builder, operator, observer. По умолчанию при добавлении назначается «оператор». null — снять роль."
    • changedInput schema / properties / role / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
  2. Changed2 schema fields changedv0.1.16
    • changedInput schema / properties / extra_permissions / items / enum
      Previous value: -[
-  "case.view",
-  "case.edit",
-  "case.delete",
-  "case.transfer",
-  "member.view",
-  "member.invite",
-  "member.edit",
-  "member.remove",
-  "role.view",
-  "role.manage",
-  "bot.view",
-  "bot.create",
-  "bot.edit",
-  "bot.delete",
-  "bot.control",
-  "bot.token_reveal",
-  "flow.view",
-  "flow.edit",
-  "flow.publish",
-  "flow.delete",
-  "chat.view",
-  "chat.reply",
-  "chat.takeover",
-  "chat.broadcast",
-  "chat.delete",
-  "ai.view",
-  "ai.manage",
-  "knowledge.view",
-  "knowledge.edit",
-  "audit.view"
-]New value: +[
+  "case.view",
+  "case.edit",
+  "case.delete",
+  "case.transfer",
+  "member.view",
+  "member.invite",
+  "member.edit",
+  "member.remove",
+  "role.view",
+  "role.manage",
+  "bot.view",
+  "bot.create",
+  "bot.edit",
+  "bot.delete",
+  "bot.control",
+  "bot.token_reveal",
+  "flow.view",
+  "flow.edit",
+  "flow.publish",
+  "flow.delete",
+  "market.publish",
+  "chat.view",
+  "chat.reply",
+  "chat.takeover",
+  "chat.broadcast",
+  "chat.delete",
+  "ai.view",
+  "ai.manage",
+  "knowledge.view",
+  "knowledge.edit",
+  "audit.view"
+]
    • changedInput schema / properties / revoked_permissions / items / enum
      Previous value: -[
-  "case.view",
-  "case.edit",
-  "case.delete",
-  "case.transfer",
-  "member.view",
-  "member.invite",
-  "member.edit",
-  "member.remove",
-  "role.view",
-  "role.manage",
-  "bot.view",
-  "bot.create",
-  "bot.edit",
-  "bot.delete",
-  "bot.control",
-  "bot.token_reveal",
-  "flow.view",
-  "flow.edit",
-  "flow.publish",
-  "flow.delete",
-  "chat.view",
-  "chat.reply",
-  "chat.takeover",
-  "chat.broadcast",
-  "chat.delete",
-  "ai.view",
-  "ai.manage",
-  "knowledge.view",
-  "knowledge.edit",
-  "audit.view"
-]New value: +[
+  "case.view",
+  "case.edit",
+  "case.delete",
+  "case.transfer",
+  "member.view",
+  "member.invite",
+  "member.edit",
+  "member.remove",
+  "role.view",
+  "role.manage",
+  "bot.view",
+  "bot.create",
+  "bot.edit",
+  "bot.delete",
+  "bot.control",
+  "bot.token_reveal",
+  "flow.view",
+  "flow.edit",
+  "flow.publish",
+  "flow.delete",
+  "market.publish",
+  "chat.view",
+  "chat.reply",
+  "chat.takeover",
+  "chat.broadcast",
+  "chat.delete",
+  "ai.view",
+  "ai.manage",
+  "knowledge.view",
+  "knowledge.edit",
+  "audit.view"
+]
  3. Changed2 schema fields changedv0.1.14
    • changedInput schema / properties / extra_permissions / items / enum
      Previous value: -[
-  "case.view",
-  "case.edit",
-  "case.delete",
-  "case.transfer",
-  "member.view",
-  "member.invite",
-  "member.edit",
-  "member.remove",
-  "role.view",
-  "role.manage",
-  "bot.view",
-  "bot.create",
-  "bot.edit",
-  "bot.delete",
-  "bot.control",
-  "bot.token_reveal",
-  "flow.view",
-  "flow.edit",
-  "flow.publish",
-  "flow.delete",
-  "chat.view",
-  "chat.reply",
-  "chat.takeover",
-  "chat.delete",
-  "ai.view",
-  "ai.manage",
-  "audit.view"
-]New value: +[
+  "case.view",
+  "case.edit",
+  "case.delete",
+  "case.transfer",
+  "member.view",
+  "member.invite",
+  "member.edit",
+  "member.remove",
+  "role.view",
+  "role.manage",
+  "bot.view",
+  "bot.create",
+  "bot.edit",
+  "bot.delete",
+  "bot.control",
+  "bot.token_reveal",
+  "flow.view",
+  "flow.edit",
+  "flow.publish",
+  "flow.delete",
+  "chat.view",
+  "chat.reply",
+  "chat.takeover",
+  "chat.broadcast",
+  "chat.delete",
+  "ai.view",
+  "ai.manage",
+  "knowledge.view",
+  "knowledge.edit",
+  "audit.view"
+]
    • changedInput schema / properties / revoked_permissions / items / enum
      Previous value: -[
-  "case.view",
-  "case.edit",
-  "case.delete",
-  "case.transfer",
-  "member.view",
-  "member.invite",
-  "member.edit",
-  "member.remove",
-  "role.view",
-  "role.manage",
-  "bot.view",
-  "bot.create",
-  "bot.edit",
-  "bot.delete",
-  "bot.control",
-  "bot.token_reveal",
-  "flow.view",
-  "flow.edit",
-  "flow.publish",
-  "flow.delete",
-  "chat.view",
-  "chat.reply",
-  "chat.takeover",
-  "chat.delete",
-  "ai.view",
-  "ai.manage",
-  "audit.view"
-]New value: +[
+  "case.view",
+  "case.edit",
+  "case.delete",
+  "case.transfer",
+  "member.view",
+  "member.invite",
+  "member.edit",
+  "member.remove",
+  "role.view",
+  "role.manage",
+  "bot.view",
+  "bot.create",
+  "bot.edit",
+  "bot.delete",
+  "bot.control",
+  "bot.token_reveal",
+  "flow.view",
+  "flow.edit",
+  "flow.publish",
+  "flow.delete",
+  "chat.view",
+  "chat.reply",
+  "chat.takeover",
+  "chat.broadcast",
+  "chat.delete",
+  "ai.view",
+  "ai.manage",
+  "knowledge.view",
+  "knowledge.edit",
+  "audit.view"
+]
  4. First observedv0.1.1

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so safety is partly covered. The description adds genuinely useful behavioral context the annotations cannot: the mode switches based on member, and the person must already be registered or the call is inappropriate. It stops short of noting what happens to existing role/notes.

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 sentences, front-loaded with the mode distinction, no filler. Every sentence carries actionable routing or prerequisite information.

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 7-parameter mutation tool with full schema coverage and annotations but no output schema, the description covers the essential modes and the registration prerequisite. It omits minor details like list-replacement semantics for permissions and return behavior, but those are adequately handled by the schema.

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 description coverage is 100%, so the per-parameter documentation already exists and the baseline would be 3. The description adds the key cross-parameter interaction (member presence flips add vs. edit), which is value beyond the individual field docs, warranting a small bump.

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 states a specific verb and resource and, critically, splits the tool into its two real modes: adding a registered person by email (no member param) vs. changing role/permissions (member param). It even names the sibling to use for the unregistered case, invites_create, so an agent can distinguish it without opening the 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 gives explicit selection logic keyed on the presence/absence of the member parameter and routes the unregistered-user scenario to invites_create. When-to-use and the primary alternative are both spelled out rather than left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools