Skip to main content
Glama
Telegram Live MCP

Telegram Live MCP

by sugestr

export_text

Read-only

Saves up to 20 specified Telegram messages to a private local file (0600) and returns the path, character count, and SHA256 hash without exposing the message text.

Instructions

Сохранить до20точных сообщений в локальный приватный файл0600. Возвращает путь, число знаков и SHA256 без самого текста.

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

Input Schema

NameRequiredDescriptionDefault
chat_idYesиз find_dialogs
message_idsYesномера сообщений из read_chat

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior1/5

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

The description is rich in behaviour (20-message cap, 0600 file permissions, returns path/character count/SHA256 instead of the text), but it states the tool writes a file to disk while the annotations declare readOnlyHint=true and destructiveHint=false. Persisting a file is an environmental side effect, which is a direct annotation contradiction, so the rule forces a score of 1.

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?

Two sentences, front-loaded with the action and destination, then the return shape; nothing is wasted. Minor loss: the collapsed spacing ('до20точных', 'файл0600') makes one pass slightly harder to parse than necessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

It does the important work of describing the return value in the absence of an output schema, and it flags the private-file handling. It leaves open what happens on more than 20 IDs (truncate vs error), where the file is written, and whether an existing file is overwritten — questions an agent calling a file-export tool would need answered.

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 100% and both parameters are already documented (chat_id from find_dialogs, message_ids from read_chat), so the baseline is 3. The description adds a real constraint the schema does not express — that at most 20 message IDs are processed — which meaningfully qualifies message_ids.

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 a specific verb and resource (save messages) plus the destination (a local private file), and the 20-message cap gives it a concrete identity that is distinct from read-only siblings such as read_chat or search_chat. An agent can tell what this tool produces without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative, even though read_chat is the obvious read-only counterpart. Only the implied 'export rather than read' framing hints at selection, and the 20-message bound is stated without saying whether callers should batch.

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