Skip to main content
Glama

Уведомления в Telegram и MAX

manage_quiz_messenger
Destructive

Настройки отправки ответов в мессенджер — Telegram или MAX. Показывает, куда именно уходят заявки: список чатов, групп и людей, тему сообщения, какие вопросы из него исключены, есть ли кнопки. Позволяет включить и выключить отправку, убрать интеграцию, убрать одного получателя, задать состав сообщения и отправить пробное. Токены здесь не вводят: бот платформенный, человек лишь добавляет его в чат по ссылке из ответа. Журнал доставки — в get_integration_logs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "quiz_id": "<quiz_id>",
      "messenger": "<messenger>",
      "action": "<action>"
    },
    "name": "manage_quiz_messenger"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesЧто сделать: show — настройки и получатели, activate — включить (и получить ссылку добавления бота), deactivate — выключить, delete — убрать интеграцию, toggle_buttons — кнопки под сообщением, save_widgets — состав сообщения и тема, remove_recipient — убрать одного получателя, test — пробное сообщение.
quiz_idYesID опроса.
subjectNoТема сообщения, до 70 символов. Применяется при save_widgets.
messengerYesКакой мессенджер: telegram или max.
recipient_idNoID получателя из show. Нужен для remove_recipient.
buttons_enabledNoПрисылать ли кнопки под сообщением. Нужно для toggle_buttons.
hidden_widget_idsNoID вопросов, которые НЕ надо включать в сообщение. Список задаётся целиком: чего в нём нет, то в сообщение вернётся. Взять из quiz://{id}/structure.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and readOnlyHint=false, so the safety profile is given. The description adds real context beyond them: no tokens are entered because the bot is platform-level, activate yields an add-to-chat link, and logs are read elsewhere. It falls short of telling the agent which of the enumerated actions are the destructive ones (delete, remove_recipient) versus the read-only show.

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?

Purpose and channel are front-loaded, followed by the capability list and the two useful caveats about tokens and logs. The middle sentence is a long run-on enumeration, but every element maps to an actual action or field, so little is wasted.

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 an eight-action destructive tool with no output schema, the description covers the capability surface, the activation link behavior, and where logs go. It does not warn about the irreversibility of delete or clarify what show returns beyond the recipient list, which would matter for a destructive multi-action tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, including a fully documented action enum and the note that hidden_widget_ids is a full replacement list. The description restates these fields (subject, excluded questions, buttons) without adding syntax or format detail, so the schema does the heavy lifting and the baseline of 3 applies.

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 names the concrete resource (sending quiz responses to Telegram or MAX) and enumerates the operations a caller can perform: show recipients, activate/deactivate, delete, remove a recipient, set message composition, send a test. It explicitly separates itself from the sibling that holds delivery history (get_integration_logs), so an agent can pick between them 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?

It gives clear context for use and one explicit routing rule: delivery history lives in get_integration_logs, and bot adding is done by link from the response rather than by token entry here. It does not state when to prefer this tool over the CRM/amoCRM mapping siblings, but those cover different channels, so the practical gap is small.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources