Skip to main content
Glama
uk-kd

operbots-mcp

by uk-kd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Настроить диалог

dialogs_update

Update dialog settings: switch between bot and operator mode, toggle AI replies, set tags, pin conversations, and assign community flow. Blocking is not available here.

Instructions

Меняет режим ведения (сценарий или оператор), отвечает ли ИИ, метки, закрепление и сценарий сообщества. Перевод в режим bot возвращает разговор сценарию и снимает оператора. Заблокировать собеседника отсюда нельзя: блокировку приносит платформа, когда человек сам закрывает боту рот, — панель её только показывает.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
caseNoДело: название или идентификатор. Если не указать, берётся дело по умолчанию, иначе последнее открытое в панели.
flowNoТолько для сообществ: свой сценарий этого чата поверх базового у бота — название или идентификатор сценария вида community у того же бота. Пустая строка — вернуть базовый.
modeNobot — вернуть сценарию; operator — вести вручную.
tagsNoМетки. Заменяют прежние целиком.
dialogYesДиалог: имя собеседника, @username, номер чата или идентификатор.
pinnedNoЗакрепить наверху списка.
ai_enabledNoОтвечает ли ИИ в этом диалоге.
assigned_operator_idNoID пользователя-оператора из members_list; null снимает назначение.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • addedInput schema / properties / assigned_operator_id
      Added value: +{
+  "anyOf": [
+    {
+      "format": "uuid",
+      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "ID пользователя-оператора из members_list; null снимает назначение."
+}
  2. Changed1 schema field changedv0.1.17
    • addedInput schema / properties / flow
      Added value: +{
+  "description": "Только для сообществ: свой сценарий этого чата поверх базового у бота — название или идентификатор сценария вида community у того же бота. Пустая строка — вернуть базовый.",
+  "type": "string"
+}
  3. Changed1 schema field changedv0.1.14
    • removedInput schema / properties / blocked
      Removed value: -{
-  "description": "Заблокировать собеседника.",
-  "type": "boolean"
-}
  4. First observedv0.1.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=false, so the safety profile is covered. The description adds genuine side-effect context beyond that: switching to bot mode removes the assigned operator, and the tool deliberately cannot block a counterparty (the platform does that). That is useful behavior disclosure.

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?

Three sentences, front-loaded with the mutation scope before the side effect and the boundary case. Every sentence carries information, though the blocking sentence is a defensive note rather than core guidance.

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 an 8-parameter mutation tool with no output schema and annotations covering the safety profile, the description covers the main operation, a key side effect, and one important limitation. It is largely complete, missing only permission/auth expectations.

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%, so the baseline is 3. The description mostly mirrors the schema's field list; the one additive nuance is that bot mode 'снимает оператора', which goes slightly beyond the schema's mode description. No format, default, or interaction detail is added.

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 names a specific verb ('Меняет') and enumerates the exact mutable fields: mode, AI response, tags, pinning, and community flow, so an agent can match it to the schema's properties immediately. It does not explicitly name a sibling, but the 'can't block from here' boundary hints at its scope versus other dialog tools.

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

Usage Guidelines3/5

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

It states a use condition implicitly (switching to bot mode returns the conversation to the scenario) and an exclusion (blocking is not done here), but never points to a concrete alternative tool for blocking or for the other dialog operations. Usage context is implied rather than spelled out.

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