fast-mcp-telegram

by io.github.leshchenko1979

Send message to phone

send_message_to_phone

Destructive

Send to a phone number: may create a temporary contact, then send text or files. Supports parse_mode: classic markdown/html/auto or rich (Rich Message; dialect auto-detected). parse_mode=rich cannot be combined with files. Success: send result plus contact_was_new / contact_removed when applicable. Full documentation: https://github.com/alexeyleshchenko/fast-mcp-telegram/blob/main/docs/Tools-Reference.md

Input Schema

TableJSON Schema

Name	Required	Description	Default
`files`	No	List of attachment URLs, local paths, or data URIs (one or more strings). data: URIs (data:<mime>;base64,<payload>) work in all server modes; local paths work in stdio mode only.
`message`	Yes	Message text. When sending files, used as caption.
`last_name`	No	Last name when creating a temporary contact.	Name
`first_name`	No	First name when creating a temporary contact.	Contact
`parse_mode`	No	'markdown'/'html'/'auto': classic entity formatting (auto detects). 'rich': Telegram Rich Message document; dialect auto-detected (known HTML tags outside code → rich HTML, else rich markdown). Default is 'auto'. parse_mode='rich' cannot be combined with files.	auto
`phone_number`	Yes	E.164 phone number with country code, e.g. +1234567890 (must be on Telegram).
`remove_if_new`	No	If true, delete the contact after send when it was created only for this send.
`reply_to_msg_id`	No	Reply to this message id in the target chat after resolve.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	No
`chat`	No
`code`	No
`date`	No
`rich`	No
`text`	No
`error`	No
`action`	No
`params`	No
`sender`	No
`status`	No
`topic_id`	No
`edit_date`	No
`exception`	No
`operation`	No
`error_code`	No
`message_id`	No
`rich_format`	No
`phone_number`	No
`reply_markup`	No
`contact_removed`	No
`contact_was_new`	No

TDQS

A4.6/5.0

Behavior5/5

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

The description discloses temporary contact creation, parse_mode behaviors, and the rich/files incompatibility, which go beyond the openWorldHint and destructiveHint annotations. It also mentions contact_was_new/contact_removed in the result, giving insight into side effects.

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 compact and front-loaded, using three sentences for purpose, mode details, and result hints, plus a documentation link. Every sentence adds unique information without redundancy.

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?

Given the tool's 8-parameter complexity and the presence of an output schema, the description covers core behaviors, constraints, and result characteristics. It could include more caveats like local-path restrictions, but the schema already covers those, making it sufficiently complete.

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%, providing a baseline 3. The description adds value by clarifying parse_mode semantics, highlighting the rich + files conflict, and noting ephemeral contact flags, exceeding baseline.

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 states 'Send to a phone number' with a specific verb and resource, clearly distinguishing it from the sibling send_message tool which likely targets chat IDs. It also mentions temporary contact creation, clarifying the tool's scope.

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?

The description implies usage when a phone number is available, which contrasts with send_message. However, it does not explicitly name alternatives or state when not to use this tool, so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All fast-mcp-telegram tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0

Disambiguation5/5

Each tool serves a distinct purpose: sending vs editing messages, per-chat vs global search, finding vs retrieving chat info, and a low-level API escape hatch. No two tools overlap in functionality.

Naming Consistency4/5

Tool names follow a consistent verb_noun pattern in snake_case (e.g., send_message, get_chat_info). Minor deviation with 'search_messages_globally' (adverb inserted) and 'invoke_mtproto' (different verb), but overall pattern is clear.

Tool Count5/5

8 tools is a well-scoped set for a Telegram assistant. It covers core operations without being overwhelming or too sparse.

Completeness3/5

Covers send, edit, read, search, and chat discovery. Missing delete and forward message tools, but the low-level invoke_mtproto can compensate. Notable gaps in common messaging workflows.

Send message to phone

Input Schema

Output Schema

TDQS

Glama MCP Gateway

TDQS

Resources