Skip to main content
Glama
Sign In
telegram-bot-mcp

telegram-bot-mcp

by FantomaSkaRus1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

send_business_message

Send a text message on behalf of a business account using a business connection ID. Specify chat ID and message text.

Instructions

Send a text message on behalf of a business account. Requires business_connection_id.

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": {
      "business_connection_id": "<business_connection_id>",
      "chat_id": "<chat_id>",
      "text": "<text>"
    },
    "name": "send_business_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesMessage text (up to 4096 characters)
chat_idYesChat ID to send message to
parse_modeNoText formatting mode. Default: none
reply_markupNoJSON string with inline keyboard markup
business_connection_idYesBusiness connection ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.3

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description carries full burden but only states basic function. No details on rate limits, error conditions, or behavioral implications beyond sending a text message.

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?

One sentence, 13 words, front-loaded with verb and resource. Highly concise with no redundant information.

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

Completeness3/5

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

Given the tool's simplicity and full schema coverage, the description is adequate but lacks context distinguishing it from personal message sending (send_message) or explaining output behavior.

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 coverage is 100%, baseline 3. The description adds no new meaning beyond the schema, merely restating the required business_connection_id.

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 specifies the action (send), resource (text message), and context (business account), clearly differentiating it from other send tools for media or non-business messages.

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 description mentions the requirement of business_connection_id, implying usage for business accounts, but does not explicitly state when to use this tool versus alternatives like send_message or other business message edit tools.

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