Skip to main content
Glama
Sign In
Copilot Desktop MCP

Copilot Desktop MCP

by avianhermana
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Send Telegram Message

send_telegram_message

Send notifications, reports, or meeting summaries directly to a Telegram user or group chat to keep collaborators informed from AI workflows.

Instructions

Send a notification, report, or meeting summary directly to a Telegram user or group chat.

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": {
      "message": "<message>"
    },
    "name": "send_telegram_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
chat_idNo
messageYes
bot_tokenNo
parse_modeNoHTML

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden but only states that a message is delivered. It does not disclose auth requirements for bot_token, what happens when chat_id is empty, rate limits, or error behavior for failed delivery.

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 efficient sentence with the purpose front-loaded; no wasted words, though the brevity reflects under-specification rather than tight editing.

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?

The presence of an output schema means return values need no explanation, but for a 4-parameter tool with 0% schema coverage and no annotations, the description leaves essential invocation details, especially authentication and chat targeting, completely unaddressed.

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

Parameters1/5

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

Schema description coverage is 0% and the description mentions no parameters. Critical fields like chat_id and bot_token default to empty strings with no explanation of how they should be populated, and parse_mode's HTML default is entirely undocumented.

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?

States a specific verb (send) and resource (Telegram message) plus the accepted content types (notification, report, meeting summary) and targets (user or group chat). It is clear, but does not distinguish itself from sibling tools like send_telegram_document or notify_user.

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?

There is no explicit guidance on when to choose this tool over send_telegram_document (for files) or notify_user, nor any exclusions or prerequisites such as needing a valid bot token or an existing chat.

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