Skip to main content
Glama
Telegram Live MCP

Telegram Live MCP

by sugestr

find_dialogs

Read-only

Find Telegram chats by partial name to retrieve the chat ID required for reading messages; flags verified linked IDs after a group becomes a supergroup and returns the current supergroup ID.

Instructions

Найти чаты аккаунта по куску названия. С этого начинается любое чтение: id чата берётся отсюда, наугад его не бывает. После переноса обычной группы в супергруппу Telegram может вернуть два id одного чата; инструмент помечает проверенную пару и указывает текущий id супергруппы. Одинакового названия без такой связи недостаточно, чтобы считать записи одной группой.

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": {
      "query": "<query>"
    },
    "name": "find_dialogs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoсколько вернуть
queryYesчасть названия, регистр не важен
refreshNoпересобрать список диалогов до поиска: нужно, когда чат создан только что; ожидание до 40 секунд, при превышении повтори вызов для продолжения обхода

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so safety is covered; the description instead contributes domain behavior: after a group-to-supergroup migration two ids can refer to one chat, the tool marks the verified pair and reports the current supergroup id. It does not describe result ordering or the exact shape of the returned list, which matters because there is no output schema.

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 short sentences, front-loaded with the core purpose and then the id-resolution rule and the migration edge case. No filler, though the last sentence about identical names is dense and would read better attached to the duplicate-id sentence.

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 three-parameter, read-only discovery tool with no output schema, the description covers purpose, the mandatory entry-point role, and the one genuinely surprising edge case (duplicate ids after supergroup migration). What it still omits is the return shape beyond the migration marking, which an agent must infer.

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%, so all three parameters (query, limit, refresh, including refresh's 40-second wait and resume instruction) are already documented in the schema. The description adds no extra meaning about case sensitivity, matching rules, or what limit defaults to, so the baseline 3 applies.

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 concrete verb and resource (find account chats by a fragment of the name) and adds a scoping claim that it is the mandatory entry point for obtaining chat ids. It distinguishes itself functionally from the read tools by saying ids come from here, though it never names those siblings explicitly.

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?

'С этого начинается любое чтение: id чата берётся отсюда, наугад его не бывает' gives a strong when-to-use rule: before any read, resolve the id here rather than guessing. It stops short of stating when-not-to-use or naming an alternative tool for cases where the chat is already known.

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