Skip to main content
Glama
aahl

MCP Server for notify to weixin / telegram / bark / lark

by aahl

Telegram send text

tg_send_message

Send text or markdown messages to a Telegram chat using a bot. Specify chat ID, parse mode, and reply to message ID.

Instructions

Send text or markdown message via telegram bot

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesText of the message to be sent, 1-4096 characters after entities parsing
chat_idNoTelegram chat id, Default to get from environment variables
parse_modeNoMode for parsing entities in the message text. [text/MarkdownV2]
reply_to_message_idNoIdentifier of the message that will be replied to

Implementation Reference

  • The core handler function for the tg_send_message tool. It sends a text/markdown message via a Telegram bot, supporting optional parse_mode (MarkdownV2) and reply_to_message_id parameters. It returns the Telegram API response as JSON.
    async def tg_send_message(
        text: str = Field(description="Text of the message to be sent, 1-4096 characters after entities parsing"),
        chat_id: str = Field("", description="Telegram chat id, Default to get from environment variables"),
        parse_mode: str = Field("", description=f"Mode for parsing entities in the message text. [text/MarkdownV2]"),
        reply_to_message_id: int = Field(0, description="Identifier of the message that will be replied to"),
    ):
        if not bot:
            return "Please set the `TELEGRAM_BOT_TOKEN` environment variable"
        if parse_mode == TELEGRAM_MARKDOWN_V2:
            text = telegramify_markdown.markdownify(text)
        res = await bot.send_message(
            chat_id=chat_id or TELEGRAM_DEFAULT_CHAT,
            text=text,
            parse_mode=parse_mode if parse_mode in [TELEGRAM_MARKDOWN_V2] else None,
            reply_to_message_id=reply_to_message_id or None,
        )
        return res.to_json()
  • Input parameters (text, chat_id, parse_mode, reply_to_message_id) are defined using Pydantic Field descriptors directly in the function signature, serving as the schema for validation.
    async def tg_send_message(
        text: str = Field(description="Text of the message to be sent, 1-4096 characters after entities parsing"),
        chat_id: str = Field("", description="Telegram chat id, Default to get from environment variables"),
        parse_mode: str = Field("", description=f"Mode for parsing entities in the message text. [text/MarkdownV2]"),
        reply_to_message_id: int = Field(0, description="Identifier of the message that will be replied to"),
    ):
        if not bot:
            return "Please set the `TELEGRAM_BOT_TOKEN` environment variable"
        if parse_mode == TELEGRAM_MARKDOWN_V2:
            text = telegramify_markdown.markdownify(text)
        res = await bot.send_message(
            chat_id=chat_id or TELEGRAM_DEFAULT_CHAT,
            text=text,
            parse_mode=parse_mode if parse_mode in [TELEGRAM_MARKDOWN_V2] else None,
            reply_to_message_id=reply_to_message_id or None,
        )
        return res.to_json()
  • The tool is registered with FastMCP via the @mcp.tool() decorator with title 'Telegram send text' and description 'Send text or markdown message via telegram bot'.
    @mcp.tool(
        title="Telegram send text",
        description="Send text or markdown message via telegram bot",
    )
  • The add_tools function is the module-level entry point that receives the FastMCP instance and registers all Telegram bot tools. It also initializes the Bot client with environment variables.
    def add_tools(mcp: FastMCP, logger=None):
        bot = Bot(
            TELEGRAM_BOT_TOKEN,
            base_url=f"{TELEGRAM_BASE_URL}/bot",
            base_file_url=f"{TELEGRAM_BASE_URL}/file/bot",
        ) if TELEGRAM_BOT_TOKEN else None
  • Top-level registration: tgbot.add_tools(mcp) is called in __init__.py to wire up the module's tools onto the FastMCP server.
    wework.add_tools(mcp)
    tgbot.add_tools(mcp)
    other.add_tools(mcp)
    hass.add_tools(mcp)
    util.add_tools(mcp)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.0
    • addedInput schema / properties / reply_to_message_id
      Added value: +{
      +  "default": 0,
      +  "description": "Identifier of the message that will be replied to",
      +  "type": "integer"
      +}
  2. First observed

TDQS

B3.2/5.0
Behavior2/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 of behavioral disclosure. It only states the action (sending a message) but does not mention side effects, rate limits, error handling, or any safety considerations. The lack of detail leaves the agent unaware of potential issues.

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 description is a single sentence, concise and front-loaded with the purpose. While efficient, it could benefit from a slightly more structured format (e.g., listing supported formats). Nonetheless, it avoids unnecessary verbosity.

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?

Given 4 parameters with full schema coverage and no output schema, the description is somewhat complete but lacks contextual details such as dependency on environment variables or authentication requirements. It does not mention that the chat_id can default from environment, which is a key context for the agent.

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 the baseline is 3. The description adds no extra meaning beyond what the schema already provides for each parameter. It does not synthesize or contextualize the parameters in the broader task.

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 sends text or markdown messages via a Telegram bot, using a specific verb ('send') and resource ('telegram bot'). It distinguishes itself from sibling tools like tg_send_audio, tg_send_photo, etc., which handle different media types.

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?

The description provides no guidance on when to use this tool versus alternatives, nor any prerequisites or conditions. For example, it doesn't mention that a bot token must be configured or that the tool relies on environment variables for default chat_id.

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