Skip to main content
Glama

Ссылка подключения бота

get_quiz_messenger_link
Read-onlyIdempotent

Ссылка, по которой человек добавляет бота Telegram или MAX в чат, чтобы туда приходили ответы опроса. Интеграцию не создаёт и отправку не включает: если интеграции ещё нет, она появится, только когда человек нажмёт «Старт» в боте по этой ссылке. connected — интеграция включена (бота добавили «Стартом» или отправку включили в кабинете). Для Telegram есть ещё group_url — добавить бота в группу. Настройки, получатели и выключение — manage_quiz_messenger.

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>"
    },
    "name": "get_quiz_messenger_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
quiz_idYesID опроса.
messengerYesКакой мессенджер: telegram или max.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered; the description goes further by disclosing the delayed side effect (the integration only materialises when a human presses «Старт» on the link) and by explaining the meaning of returned fields such as connected and the Telegram-only group_url. That is real behavioral context an agent could not derive from 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?

The purpose is front-loaded in the first clause and every sentence carries information. It is dense and semicolon-heavy, packing return-field semantics and the alternative-tool pointer into one block, which slightly hurts scanability but wastes no words.

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 two-parameter read-only link getter with no output schema, the description covers everything needed: what the link does, that nothing is created or enabled, the meaning of connected and group_url, and where to go for configuration. An agent can call it correctly and interpret the result from the description alone.

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% and the enum already lists telegram/max, so the schema carries the parameter meaning. The prose mentions the messenger choice and the Telegram-specific group_url, but adds no syntax or constraints for quiz_id or messenger beyond what the schema states; baseline 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 exact resource (a connection link that adds a Telegram or MAX bot to a chat so quiz responses arrive there), not just a getter. It immediately separates itself from the sibling that configures things by pointing to manage_quiz_messenger, so an agent can pick between them without opening either schema.

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 states both when to use this tool and what it does NOT do: it does not create the integration and does not enable sending — that only happens after the person presses «Старт» in the bot. It also explicitly routes settings, recipients and disabling to manage_quiz_messenger, giving a clear alternative with its selecting condition.

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