Skip to main content
Glama
Sign In
telegram-mcp

telegram-mcp

by draiqw
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

tg_send

Send a Telegram message to a specified chat, visible to the recipient immediately. Supports optional reply-to and silent delivery to avoid notification sounds.

Instructions

Send a message as the user. This is visible to the recipient immediately.

Confirm the exact chat and wording with the user before calling, unless they already approved this specific message.

Args: chat: chat id, @username, exact title, or "me" for Saved Messages. text: message body (max 4096 chars). reply_to: message id to reply to. silent: deliver without a notification sound.

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>",
      "text": "<text>"
    },
    "name": "tg_send"
  }
}

Input Schema

NameRequiredDescriptionDefault
chatYes
textYes
silentNo
reply_toNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses that the message is sent as the user, is immediately visible, and requires prior user confirmation. It also specifies the 4096-char limit. It does not cover error behavior or reversibility, but covers key behavioral traits for a send action.

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 front-loaded with purpose, followed by a critical safety instruction, then a concise parameter list. Every sentence earns its place with no redundancy or filler.

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

Completeness5/5

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

For a four-parameter send tool with an output schema present, the description covers the action, parameter formats, and the user-confirmation requirement. It provides sufficient context for an agent to invoke it correctly without needing to inspect output schema or infer hidden semantics.

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 has zero descriptions, and the description fully compensates by documenting each parameter: accepted chat identifiers, text length limit, reply_to semantics, and silent behavior. This goes far beyond the schema's type and title info.

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 uses a specific verb phrase 'Send a message as the user' and notes immediate visibility, clearly distinguishing from siblings like tg_schedule and tg_send_file. The resource (message) and scope (as user) are explicit.

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?

Provides clear context that this is for immediate message sending and includes a user-confirmation requirement. However, it does not explicitly name alternatives or exclusions (e.g., 'use tg_schedule for scheduled messages'), so it lacks explicit when-not-to-use guidance.

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