Skip to main content
Glama
Sign In
telegram-mcp-server

telegram-mcp-server

by Schimmilab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

send_file

Send a local file to any Telegram chat with an optional caption using your own user account.

Instructions

Send a local file (image/document) to a chat as the logged-in user.

This is a real, irreversible send, visible to the chat's members, and cannot be recalled via this API — confirm the chat and file before calling.

Args: chat: Chat id/@username/title. file_path: Absolute path to an existing local file. caption: Optional caption text.

Returns {"sent": True, "message_id": }.

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>",
      "file_path": "<file_path>"
    },
    "name": "send_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
chatYes
captionNo
file_pathYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

No annotations provided, but description fully discloses irreversibility, visibility to members, and inability to recall. This is thorough for a mutation operation.

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?

Description is well-structured with a main sentence, a warning paragraph, and an Args section. Every sentence is informative and not redundant.

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?

Covers action, parameters, and return format. Lacks details like file size limits or supported formats, but these are reasonable omissions given the tool's simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but description adds meaning: chat as id/@username/title, file_path as absolute path to existing file, caption as optional. This compensates fully.

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 the tool sends a local file to a chat as the logged-in user, specifying the resource and context. It differentiates from siblings like send_message (text) and other tools.

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

Usage Guidelines4/5

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

Explicitly advises confirming chat and file before calling due to irreversibility, providing clear usage context. Does not explicitly exclude alternatives, but siblings are available.

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