Skip to main content
Glama
uk-kd

operbots-mcp

by uk-kd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

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

dialogs_update

Update conversation settings: switch between bot and operator handling, toggle AI responses, set labels, pin dialogs, or assign a community scenario.

Instructions

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.17
    • addedInput schema / properties / flow
      Added value: +{
+  "description": "Только для сообществ: свой сценарий этого чата поверх базового у бота — название или идентификатор сценария вида community у того же бота. Пустая строка — вернуть базовый.",
+  "type": "string"
+}
  2. Changed1 schema field changedv0.1.14
    • removedInput schema / properties / blocked
      Removed value: -{
-  "description": "Заблокировать собеседника.",
-  "type": "boolean"
-}
  3. First observedv0.1.1

TDQS

A4.7/5.0
Behavior5/5

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

It discloses important behavior beyond the annotations: switching to bot mode returns the conversation to the scenario and removes the operator, and the tool cannot perform blocking. This materially helps an agent predict side effects. Annotations do not contradict the description.

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?

The description is compact: the first sentence front-loads the capability list, the second clarifies an important side effect, and the third sets a scope boundary. Every sentence earns its place without repetition or padding.

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 7-parameter update tool with detailed input-schema descriptions and annotations covering the safety profile, this description is sufficiently complete: it gives a general capability map, key side effects, and a scope limitation. Return values are not described, but there is no output schema to satisfy and this is a mutation tool.

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 coverage is 100%, so the baseline is 3. The description adds value by tying plain-language concepts (mode, AI, tags, pinning, community flow) to parameters and clarifying that bot mode removes the operator. It does not add detail to every parameter, but the schema already handles the rest.

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 uses a specific verb ('Меняет') and enumerates the exact dialog aspects it changes: mode, AI answering, tags, pinning, and community flow. This clearly distinguishes it from siblings like dialogs_reply, dialogs_edit_message, or dialogs_reset_stage, even without naming them.

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

Usage Guidelines4/5

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

The description makes it clear this is the tool for updating dialog configuration fields and explicitly states a non-goal: blocking an interlocutor cannot be done here. However, it does not explicitly point to alternatives for adjacent operations, so the guidance is strong but not fully explicit about sibling routing.

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