Skip to main content
Glama
Sign In
ChatPush MCP Server

ChatPush MCP Server

Official
by ChatPush
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Send message

send_message

Send text messages to a person or group chat via WhatsApp, Telegram, SMS, VK/OK, or MAX, with channel fallback, scheduling, priority, replies, typing simulation, and delivery callbacks.

Instructions

Send a text message via WhatsApp, Telegram (tdlib), Telegram Bot, SMS, VK/OK (notify), or MAX (max), with optional cascade fallback between channels. Supports scheduling, priority, reply-to, typing simulation, and delivery callbacks.

Use it when the user asks to text, message, notify or reply to one person or group chat. For many phone numbers use send_bulk; for documents, images, audio or video use send_file.

Recipient: phone is required, except for personal Telegram (dispatch_routing ["tdlib"]) where username or tdlib_user_id can be used instead, and WhatsApp where whatsapp_lid can be used.

Returns the delivery ID for get_delivery_status and delete_delivery.

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

Input Schema

NameRequiredDescriptionDefault
textYesMessage text. Max 3500 chars for messengers, 160 for one SMS segment in Latin characters.
phoneNoRecipient phone in international format, e.g. 79991234567. Optional if username/tdlib_user_id is used for tdlib.
priorityNoSending priority. Chosen automatically if omitted.
usernameNoTelegram username (format: username or @username). tdlib only.
utm_markNoLabel for tracking dispatches (see get_utm_tags).
external_idNoYour client-side ID for this message (idempotency ID).
sender_nameNoRegistered SMS sender name (see get_balance → sender names).
callback_urlNoURL that receives the final delivery status as a POST request (retried every 2 minutes, up to 10 times, until it returns HTTP 200).
scheduled_atNoDelayed sending time, format YYYY-MM-DD HH:MM:SS in UTC+0. At least 1 minute and at most 1 month ahead.
whatsapp_lidNoWhatsApp LID. Format: 43445322325 or 43445322325@lid. WhatsApp only.
tdlib_user_idNoTelegram user ID (positive = private chat, negative = group chat). tdlib channel only.
simulate_typingNoDefault true: show a typing indicator in WhatsApp before sending. false sends instantly.
dispatch_routingNoChannels in the order ChatPush should try them (cascade: the next channel is used only if delivery through the previous one fails). whatsapp = WhatsApp, tdlib = personal Telegram account, telegram = Telegram Bot, notify = VK/OK, max = MAX messenger, sms = SMS. If omitted, the account's default routing is used.
reply_to_message_idNoID of the message to reply to, taken from an incoming-message webhook.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare mutation, open-world, non-idempotent and non-destructive, so the description does not need to restate safety. It does add real behavioral context: cascade ordering semantics, fallback-on-failure behavior, scheduling window constraints, and the fact that it returns a delivery ID consumable by get_delivery_status/delete_delivery. It omits error/permission behavior and what happens when all cascade channels fail, which keeps it below a 5.

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?

Front-loaded with the core action and channel list, then usage guidance, then recipient rules, then the return value — a logical order with no filler. The first sentence is dense with feature enumeration but every clause carries distinct information.

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

Completeness4/5

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

For a 14-parameter, high-complexity messaging tool with no output schema, the description covers purpose, alternatives, recipient edge cases, and the return value. It leaves a small gap around failure modes when the cascade exhausts and around rate limits, but nothing essential for correct invocation is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds a conditional requirement that the schema cannot express: phone is required except for personal Telegram (username/tdlib_user_id) and WhatsApp (whatsapp_lid). That clarifies a genuinely ambiguous required-field matrix across 14 parameters.

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?

States a specific verb+resource ('Send a text message') and enumerates the supported channels and capabilities (cascade fallback, scheduling, priority, reply-to, typing simulation, callbacks). It is clearly distinguishable from send_bulk and send_file, which are named as the alternatives for different payloads.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use ('when the user asks to text, message, notify or reply to one person or group chat') plus explicit when-to-use-an-alternative for both siblings (send_bulk for many phone numbers, send_file for documents/images/audio/video). Recipient preconditions are also spelled out per channel.

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