Skip to main content
Glama
uk-kd

operbots-mcp

by uk-kd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Прогнать сценарий

flows_simulate

Simulate a flow scenario to see which trigger fires, steps executed, and bot replies without saving the dialog or performing external actions. Pass conversation variables to test conditional branches and substitutions.

Instructions

Проверяет сценарий, не выходя к платформе: какой триггер сработал, какие шаги прошли и что бот ответил бы. Диалог нигде не сохраняется, задержки пропускаются, запросы к внешним адресам и весточки в служебный чат не выполняются. Через variables можно подставить накопленное разговором — так проверяются ветки условий и подстановки. Внимание: узлы с ИИ обращаются к настоящей модели и расходуют её лимиты.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
botYesБот: название, @username или идентификатор.
caseNoДело: название или идентификатор. Если не указать, берётся дело по умолчанию, иначе последнее открытое в панели.
flowYesСценарий: название или идентификатор.
textNoТекст входящего сообщения.
eventNoДля сценариев сообществ: post — пост в канале (text — его текст), join и leave — участник вошёл или вышел (text — его имя). Без него — обычное сообщение.
commandNoКоманда без косой черты, например start.
variablesNoПеременные разговора на момент прогона: {"город": "Москва"}.
callback_dataNoДанные нажатой кнопки.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.17
    • addedInput schema / properties / event
      Added value: +{
+  "description": "Для сценариев сообществ: post — пост в канале (text — его текст), join и leave — участник вошёл или вышел (text — его имя). Без него — обычное сообщение.",
+  "enum": [
+    "post",
+    "join",
+    "leave"
+  ],
+  "type": "string"
+}
  2. Changed1 schema field changedv0.1.13
    • addedInput schema / properties / variables
      Added value: +{
+  "additionalProperties": {},
+  "description": "Переменные разговора на момент прогона: {\"город\": \"Москва\"}.",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
  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?

The description substantially expands on the annotations by disclosing that the dialog is not saved, delays are skipped, external requests and service-chat messages are not executed, and AI nodes call the real model and consume quota. This is exactly the behavioral context an agent needs beyond readOnlyHint/openWorldHint, and nothing contradicts 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?

Four dense, purposeful sentences: purpose first, then behavioral caveats, then the variables use case, then the AI quota warning. Every sentence contributes new information and the description does not repeat schema content.

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 complex simulation tool with 8 parameters and no output schema, the description covers expected results, side-effect limitations, parameter semantics for variables, and a critical cost warning about AI node usage. Combined with the fully described schema, an agent has enough context to select and invoke the tool correctly.

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?

The input schema already covers all 8 parameters with descriptions, so the baseline is 3. The description adds meaningful extra semantics for variables — they substitute accumulated conversation values to test condition branches and substitutions — and emphasizes that the tool is a simulation, which clarifies how parameters like text, event, or command are interpreted.

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?

States a concrete verb and resource: 'Проверяет сценарий' and describes what the simulation returns — which trigger fired, which steps passed, and what the bot would reply. This clearly distinguishes it from sibling flow tools like flows_get, flows_publish, or flows_delete by framing it as a non-publishing simulation tool.

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?

Gives clear usage context: use it to test scenarios and condition/substitution branches via variables without persisting the dialog or hitting external endpoints. It does not explicitly name alternative tools or state when not to use it, but the intended use case is evident from the description.

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