Skip to main content
Glama
Telegram Live MCP

Telegram Live MCP

by sugestr

read_chat

Read-only

Read Telegram chat messages for a specified period and return date, author, sender ID, username when available, and text to support group-content review and analysis.

Instructions

Прочитать сообщения чата за период. Возвращает дату, автора, sender_id и @username (когда доступны), текст. Для разбора «что полезного было в группе» бери период пошире и читай подряд.

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": {
      "chat_id": "<chat_id>"
    },
    "name": "read_chat"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoза сколько последних суток, по умолчанию 30
limitNoсколько сообщений, до 3000
sinceNoГГГГ-ММ-ДД, вместо days
untilNoГГГГ-ММ-ДД
chat_idYesиз find_dialogs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds value beyond that by disclosing the return shape (date, author, sender_id, @username when available, text), which matters because there is no output schema. It does not mention truncation, ordering, or rate limits.

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?

Three short sentences with the action and return fields front-loaded and the usage tip last. Nothing is padded, though the return-field enumeration could be marginally tightened.

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 five-parameter read tool with no output schema, the description covers both what is read and what comes back, which is the main gap such tools usually leave. Ordering, pagination/truncation behavior and the distinction from search_chat remain undocumented.

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 five parameters (days, limit, since, until, chat_id) are already documented in the schema. The description only adds a loose tactic ('бери период пошире') that touches on days/limit, without format or interaction details, 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?

The first sentence gives a specific verb+resource ('Прочитать сообщения чата за период') and the second enumerates the returned fields, so an agent knows exactly what it gets. It does not name or contrast against the obvious sibling search_chat, so differentiation is left implicit.

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?

It supplies one concrete usage scenario ('для разбора «что полезного было в группе»') with a tactic for that case (wider period, read in sequence). There is no explicit when-not-to-use guidance and no named alternative such as search_chat for targeted lookups.

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