Copilot Desktop MCP

Overview Schema Source Related Servers Discussions Admin

Send Telegram Document

send_telegram_document

Send generated Excel, Word, PowerPoint, or PDF documents directly to Telegram with optional captions and chat targeting.

Instructions

Send a generated document (Excel .xlsx, Word .docx, PowerPoint .pptx, or PDF) directly to Telegram.

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

Input Schema

Name	Required	Description	Default
`caption`	No
`chat_id`	No
`bot_token`	No
`file_path`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 10, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full burden, and it discloses almost nothing behavioral: no auth requirements, no statement about what an empty chat_id or bot_token does (environment fallback?), no file-size or rate limits, and no failure semantics if file_path is wrong. Only supported file formats are communicated.

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?

A single front-loaded sentence with the verb, resource, and accepted formats in order — no filler. It is efficient, though its brevity is partly the cause of the missing semantics rather than a virtue of tight writing.

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?

Output schema exists so return values need not be described, but for a write/send action with zero annotations and three undocumented optional parameters, the definition leaves too much unknown about credentials, defaults, and error behavior for an agent to call it confidently.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate and it does not: caption, chat_id, and bot_token are all left unexplained, including the critical question of whether their empty-string defaults trigger a configured default chat/bot. Only file_path gains any meaning, and that only indirectly through the format list.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ("Send") and a specific resource ("a generated document"), and enumerates supported formats (.xlsx, .docx, .pptx, PDF), which implicitly separates it from send_telegram_message. It does not explicitly name that sibling as the alternative, so it stops short of the top mark.

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 word "generated" faintly implies the post-creation step, but there is no explicit when-to-use, no when-not-to-use, and no mention of the obvious sibling send_telegram_message for plain text. An agent must infer the routing decision entirely on its own.

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

Deploy Server