Skip to main content
Glama
uk-kd

operbots-mcp

by uk-kd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Переменные контента бота

bots_variables_set

Set or update variables for bot script texts, including prices, addresses, and links. Mark secrets to hide them.

Instructions

Задаёт переменные, которые подставляются в тексты сценария: цены, адреса, ссылки. Существующие ключи обновляются, новые создаются. Отмеченные секретными не показываются обратно. Ключ: латиница, цифры, подчёркивание и точка.

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.2.0
    • addedInput schema / properties / variables / items / properties / description / anyOf
      Added value: +[
+  {
+    "maxLength": 240,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / variables / items / properties / description / description
      Previous value: -"Для чего она."New value: +"Для чего она. null — стереть описание."
    • removedInput schema / properties / variables / items / properties / description / maxLength
      Removed value: -240
    • removedInput schema / properties / variables / items / properties / description / type
      Removed value: -"string"
    • changedInput schema / properties / variables / items / properties / value / description
      Previous value: -"Значение."New value: +"Значение. Обязательно для новой переменной; без него существующее сохраняется."
    • changedInput schema / properties / variables / items / required
      Previous value: -[
-  "key",
-  "value"
-]New value: +[
+  "key"
+]
  2. First observedv0.1.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations cover safety (readOnly=false, destructive=false, openWorld=true), and the description adds meaningful context beyond them: upsert behavior, that secret-marked values are not returned back, and the allowed key charset. This is genuine behavioral disclosure not found in the structured fields.

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?

Four tight sentences with the core action front-loaded, followed by upsert, secrecy, and key-format details in order of importance. Dense and free of filler, though a slightly more explicit routing sentence could be added.

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?

With no output schema, the description still covers upsert semantics, secret-value behavior, and key constraints, which is enough for an agent to call a 4-parameter mutation correctly. Only explicit when-to-use guidance is missing.

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 already 100%, so the baseline is 3, but the description adds the key character-set rule (Latin letters, digits, underscore, dot) that the schema only illustrates with a single example, plus the secret round-trip caveat. That is added value beyond the schema.

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?

States a specific verb+resource (sets the variables substituted into scenario texts) and clarifies what those variables are (prices, addresses, links). It is clearly distinguishable from sibling bots_* tools, though it does not explicitly name an alternative.

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?

Usage is implied through the upsert semantics (existing keys update, new ones are created), which tells the agent this is the write path for variables. However, there is no explicit when-to-use vs alternatives guidance or prerequisites, so it stays at the minimum viable level.

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