claude-telegram-interactive-mcp

Overview Schema Source Related Servers Discussions Admin

Send Telegram Document

send_telegram_document

Send a document or file to a Telegram chat via bot, using local Windows paths or HTTP URLs. Supports captions, custom filenames, and formatting.

Instructions

Send a document/file via Telegram bot (supports local Windows paths and HTTP URLs)

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": {
      "document": "<document>"
    },
    "name": "send_telegram_document"
  }
}

Input Schema

Name	Required	Description	Default
`chatId`	No	Optional override for target Telegram Chat ID
`caption`	No	Document caption with formatting support
`document`	Yes	Local file path (e.g. C:/path/to/file.txt) or HTTP(S) URL
`filename`	No	Custom filename for the document
`parseMode`	No	Caption formatting mode (default: HTML)	HTML

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 7, 2026

TDQS

B3.4/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 reveals that sending occurs but does not mention authentication requirements, failure behavior, external network effects, response shape, or any side effects. The path/URL support is input handling rather than behavioral transparency.

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 a single, readable, front-loaded sentence with no filler. It communicates the core purpose and a key input constraint efficiently.

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

Completeness2/5

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

For a tool with five parameters, no annotations, and no output schema, the description is too sparse. It omits guidance on optional parameters like chatId, caption, filename, and parseMode, as well as defaults, expected behavior, and prerequisites, leaving an agent without enough context to call it confidently.

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 schema already documents all five parameters and their meanings. The description's mention of 'local Windows paths and HTTP URLs' repeats what the schema already states for the 'document' parameter, adding no new semantic value.

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 states a specific verb ('Send'), a clear resource ('document/file'), and the channel ('via Telegram bot'), and it adds supported input forms (local Windows paths and HTTP URLs). This distinguishes it from sibling tools like send_telegram_photo, send_telegram_video, and send_markdown_message_as_telegram_bot.

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 use case is implied by the action: if you need to send a document or file via Telegram, use this tool. However, the description gives no explicit guidance on when to prefer this over alternatives, nor does it mention exclusions or prerequisites.

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

Deploy Server