Skip to main content
Glama
uk-kd

operbots-mcp

by uk-kd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Справочники панели

operbots_catalog
Read-onlyIdempotent

Look up scenario-building references: platform limits, node kinds with settings, market categories, AI services, and permissions.

Instructions

Что можно использовать при сборке: платформы с их пределами, виды узлов сценария с полным составом их настроек, разделы маркета, виды ИИ-сервисов с нужными ключами и каталог прав. Готовые сценарии ищите в маркете: market_list и market_install. Смотрите node_kinds перед тем, как собирать или править сценарий: config каждого узла описан именно там — и передавайте platform: сами узлы у платформ одни и те же, а варианты в их настройках разные (у MAX нет разметки MarkdownV2 и голосового среди вложений).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoПоказать подробно только один вид: например action.ai или openai.
whatYesКакой справочник показать.
scopeNoДля node_kinds: под какой вид сценария — dialog (личная переписка) или community (группы и каналы). Без него — узлы обоих видов, у каждого поле scopes.
platformNoДля node_kinds: под какую платформу отобрать варианты настроек. Без него придёт полный набор, и сценарий можно собрать с вариантом, которого у платформы бота нет.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.17
    • addedInput schema / properties / scope
      Added value: +{
+  "description": "Для node_kinds: под какой вид сценария — dialog (личная переписка) или community (группы и каналы). Без него — узлы обоих видов, у каждого поле scopes.",
+  "enum": [
+    "dialog",
+    "community"
+  ],
+  "type": "string"
+}
  2. Changed2 schema fields changedv0.1.16
    • addedInput schema / properties / platform
      Added value: +{
+  "description": "Для node_kinds: под какую платформу отобрать варианты настроек. Без него придёт полный набор, и сценарий можно собрать с вариантом, которого у платформы бота нет.",
+  "enum": [
+    "telegram",
+    "max"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / what / enum
      Previous value: -[
-  "node_kinds",
-  "flow_templates",
-  "ai_kinds",
-  "permissions"
-]New value: +[
+  "platforms",
+  "node_kinds",
+  "market_categories",
+  "ai_kinds",
+  "permissions"
+]
  3. First observedv0.1.1

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the readOnly/openWorld/idempotent annotations, the description explains what kind of data is returned for each catalog and warns that omitting platform returns the full option set, which can lead to invalid scenario settings. It also notes a concrete platform difference (MAX lacks MarkdownV2 and voice attachments).

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 dense sentences carry a lot of useful routing and parameter guidance without repeating schema content. It is slightly long, but every clause earns its place and the catalog contents are front-loaded.

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 read-only reference tool with no output schema, the description gives enough context about contents, when to use it, and how to avoid invalid node configurations. It does not describe the return format or pagination, but these are less critical for a catalog tool with rich annotations.

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 description does not need to re-document the parameters. It adds value by advising the agent to pass platform with node_kinds and explaining why (nodes are shared, setting variants differ by platform).

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 specifies the resource domain by enumerating the catalogs: platforms with limits, node_kinds with configs, market sections, AI service kinds, and permission catalog. It stops short of an explicit verb like 'returns' or 'lists', but the intent is clear and it distinguishes itself from market_list by pointing ready-made scenarios there.

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 routing: ready-made scenarios belong to market_list/market_install, while node_kinds should be consulted before building or editing a scenario. It also tells the caller to pass platform so they don't select settings unsupported by the target platform.

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