Skip to main content
Glama
uk-kd

operbots-mcp

by uk-kd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Настроить меню команд

bots_commands_apply

Sync a bot's command menu to a provided list: add missing, update existing, and reorder commands. Optionally remove unlisted commands and push updates to the platform.

Instructions

Приводит меню команд бота к переданному списку: недостающие команды добавляет, существующие обновляет, порядок расставляет по порядку в списке. Команды, которых нет в списке, сохраняются — чтобы удалить их, передайте remove_missing=true. Само меню у платформы обновляется, только если sync=true или бот перезапущен.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
botYesБот: название, @username или идентификатор.
caseNoДело: название или идентификатор. Если не указать, берётся дело по умолчанию, иначе последнее открытое в панели.
syncNoСразу отправить меню платформе. По умолчанию да.
commandsYesЖелаемое меню целиком, в нужном порядке.
remove_missingNoУдалить команды бота, которых нет в списке. По умолчанию нет.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.2.0
    • changedInput schema / properties / commands / items / properties / flow / description
      Previous value: -"Сценарий, который запускает команда."New value: +"Сценарий, который запускает команда. null — отвязать."
    • changedInput schema / properties / commands / items / properties / flow / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / commands / items / properties / node_id / description
      Previous value: -"Узел сценария, с которого начать."New value: +"Узел сценария, с которого начать. null — очистить."
    • changedInput schema / properties / commands / items / properties / node_id / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
  2. Changed2 schema fields changedv0.1.16
    • changedInput schema / properties / commands / items / properties / description / description
      Previous value: -"Пояснение в меню Telegram."New value: +"Пояснение в меню бота."
    • changedInput schema / properties / sync / description
      Previous value: -"Сразу отправить меню в Telegram. По умолчанию да."New value: +"Сразу отправить меню платформе. По умолчанию да."
  3. First observedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare the coarse profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true). The description adds real behavioral nuance the annotations cannot convey: additive-by-default semantics, the opt-in deletion path, and the deferred-sync timing. It stops short of noting auth/permission requirements, so not a 5.

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 tightly packed sentences with no filler; the core reconciliation behavior is front-loaded, followed by the two flags that modify it. Every clause carries distinct 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 5-param non-mutating-looking yet actually write tool with no output schema and full schema coverage, the description covers the divergent default behaviors an agent would otherwise get wrong. Return-value behavior is unstated, but with no output schema that gap is minor.

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, but the description adds behavioral meaning to two key params beyond their schema text — remove_missing governs preservation of unlisted commands and sync governs when the platform is actually updated. The commands array is correctly framed as the complete desired menu in order.

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 precise verb and resource ('приводит меню команд бота к переданному списку') and immediately decomposes it into add/update/reorder semantics. An agent can distinguish this reconciliation tool from siblings like bots_save or bots_detach without opening a schema.

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 concrete conditions: commands absent from the list are preserved unless remove_missing=true, and the platform menu only refreshes with sync=true or a bot restart. It does not name an alternative sibling, but the when-to-use context is explicit rather than implied.

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