Skip to main content
Glama
al-one

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

Telegram send file

tg_send_file

Send files to a Telegram chat using a bot. Supports file URLs, captions, and message threading.

Instructions

Send general files via telegram bot

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesFile URL
chat_idNoTelegram chat id, Default to get from environment variables
captionNoFile caption, 0-1024 characters after entities parsing
parse_modeNoMode for parsing entities in the caption. [text/MarkdownV2]
reply_to_message_idNoIdentifier of the message that will be replied to

Implementation Reference

  • The tg_send_file async function that handles sending files via Telegram bot. It accepts url, chat_id, caption, parse_mode, and reply_to_message_id parameters, optionally converts caption using MarkdownV2, then calls bot.send_document() and returns the result as JSON.
    async def tg_send_file(
        url: str = Field(description="File URL"),
        chat_id: str = Field("", description="Telegram chat id, Default to get from environment variables"),
        caption: str = Field("", description="File caption, 0-1024 characters after entities parsing"),
        parse_mode: str = Field("", description=f"Mode for parsing entities in the caption. [text/MarkdownV2]"),
        reply_to_message_id: int = Field(0, description="Identifier of the message that will be replied to"),
    ):
        if parse_mode == TELEGRAM_MARKDOWN_V2:
            caption = telegramify_markdown.markdownify(caption)
        res = await bot.send_document(
            chat_id=chat_id or TELEGRAM_DEFAULT_CHAT,
            document=url,
            caption=caption or None,
            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 @mcp.tool() decorator registering tg_send_file as an MCP tool with title 'Telegram send file' and description 'Send general files via telegram bot'.
    @mcp.tool(
        title="Telegram send file",
        description="Send general files via telegram bot",
    )
  • Registration of the tgbot module's tools (including tg_send_file) via tgbot.add_tools(mcp).
    wework.add_tools(mcp)
    tgbot.add_tools(mcp)
  • The add_tools function that registers all Telegram tools on the FastMCP instance, including the bot initialization.
    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
  • Pydantic Field definitions for tg_send_file parameters: url (str), chat_id (str), caption (str), parse_mode (str), reply_to_message_id (int).
    async def tg_send_file(
        url: str = Field(description="File URL"),
        chat_id: str = Field("", description="Telegram chat id, Default to get from environment variables"),
        caption: str = Field("", description="File caption, 0-1024 characters after entities parsing"),
        parse_mode: str = Field("", description=f"Mode for parsing entities in the caption. [text/MarkdownV2]"),
        reply_to_message_id: int = Field(0, description="Identifier of the message that will be replied to"),
    ):
Behavior2/5

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

No annotations provided, so the description carries full burden. It only states 'send' without disclosing file size limits, supported formats, required authentication, or whether the operation is destructive. This is insufficient for an agent to understand behavioral traits.

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?

Single sentence, front-loaded with the action, no wasted words. Extremely concise and to the point.

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?

With no output schema and no annotations, the description is adequate for differentiating from siblings but lacks details on return values, error handling, or URL formatting requirements. It covers the basics but has clear gaps.

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?

Input schema has 100% coverage with individual parameter descriptions. The description adds no extra meaning beyond the schema, providing a baseline 3. It does not explain what 'general files' entails or how parameters interact.

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 'Send general files via telegram bot' clearly states the action (send), resource (general files), and channel (telegram bot). It effectively distinguishes from siblings like tg_send_photo (specific to photos) and tg_send_message (text messages).

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?

No explicit guidance on when to use this tool versus alternatives. While siblings suggest it's for files not covered by specialized tools (audio, photo, video, message), the description does not state this directly or provide when-not-to-use scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/al-one/mcp-notify'

If you have feedback or need assistance with the MCP directory API, please join our Discord server