Skip to main content
Glama
Sign In
telegram-mcp

telegram-mcp

by draiqw
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

tg_message

Retrieve a full Telegram message's details, including reactions, inline button actions, read count, plus optional surrounding messages and reply thread.

Instructions

One message in full: reactions, inline buttons, how many people read it, plus optional surrounding context and its reply thread.

Args: chat: chat id, @username, exact title or "me". message_id: the message to inspect. context: also return this many messages before and after it. replies: also return this many replies to it (threads/comments).

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": "<chat>",
      "message_id": "<message_id>"
    },
    "name": "tg_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
chatYes
contextNo
repliesNo
message_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It describes the return content (reactions, buttons, read counts, context, replies), but does not disclose potential side effects, permission requirements, or rate limiting. It is a read operation, but this is not explicitly stated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and well-structured: a one-sentence summary followed by a clear Args list. No fluff, every line serves a purpose.

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?

Given the tool's complexity (4 params, no annotations) and presence of an output schema, the description covers the essentials. It explains parameters and scope, though it could mention default behavior (already in schema) or limitations.

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?

The schema has no parameter descriptions (0% coverage), so the description's Args block adds value by explaining each parameter: chat with examples, message_id purpose, context and replies meaning. It could be more detailed on formats, but it compensates well for the schema gap.

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 clearly states it returns a single message in full, including reactions, inline buttons, read count, and optional context/replies. The verb 'inspect' is implied, and it distinguishes itself from siblings by focusing on one message with rich detail.

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?

The description implies when to use it—when you need full details of a single message—but does not explicitly mention alternatives or exclusions. It lacks 'use this instead of X' guidance, which is important given many siblings.

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

Deploy Server

Other Tools