Skip to main content
Glama
Sign In
claude-telegram-interactive-mcp

claude-telegram-interactive-mcp

by makarworld
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Send Telegram Message in Markdown/HTML format

send_markdown_message_as_telegram_bot

Send a formatted message through a Telegram bot using HTML or Markdown, with optional chat ID override for targeting specific chats or delivering notifications.

Instructions

Send a message using Telegram bot in HTML or Markdown format (default: HTML)

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": {
      "messageText": "<messageText>"
    },
    "name": "send_markdown_message_as_telegram_bot"
  }
}

Input Schema

NameRequiredDescriptionDefault
chatIdNoOptional override for target Telegram Chat ID
parseModeNoMessage formatting mode: HTML (recommended), MarkdownV2, or Markdown (legacy)HTML
messageTextYesMessage text (HTML or Markdown)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/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 it only states the basic sending action and default parse mode. It does not disclose that this is a side-effecting network call, what prerequisites exist (bot token/configuration), what happens on invalid formatting, or what chat is used when the optional chatId is omitted.

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 front-loaded sentence that states the action, target, format options, and default. Every word earns its place and there is no redundant fluff.

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 schema covers parameter details, but the description omits important operational context: what happens when chatId is omitted, expected response or error behavior, and any authentication/config assumptions. For a side-effecting tool with no output schema and no annotations, the description is too thin to fully guide an agent.

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?

All three parameters already have rich descriptions in the JSON schema, including the enum for parseMode and its default. The description adds no meaning beyond restating the HTML default, so the baseline 3 for full schema coverage is appropriate.

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 action ('Send a message'), the resource ('Telegram bot'), and the specific formatting modes (HTML/Markdown) with a default. This cleanly distinguishes it from sibling media-sending tools like send_telegram_document, send_telegram_photo, and send_telegram_video.

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 tool's intended use is implied by the name and the format mention—formatted text messages as opposed to media or confirmations—but no explicit when-to-use or when-not-to-use guidance is provided, and no alternatives are named. Sibling names offer only implicit contrast.

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