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

telegram-bot-mcp

by FantomaSkaRus1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

forward_message

Forward a message between chats using source chat ID and message ID. Choose target chat, silent delivery, content protection, or topic thread. Defaults to log group.

Instructions

Forward a message from one chat to another. If chat_id is omitted, forwards to the default log group.

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": {
      "from_chat_id": "<from_chat_id>",
      "message_id": "<message_id>"
    },
    "name": "forward_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
chat_idNoTarget chat ID. Optional — defaults to log group
message_idYesMessage ID to forward
from_chat_idYesSource chat ID
protect_contentNoProtect message from forwarding/saving
message_thread_idNoTopic/thread ID for supergroups with topics enabled
disable_notificationNoSend silently without notification

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.3

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description bears full responsibility for behavioral disclosure. It only states the forwarding action and default chat, omitting traits such as permission requirements, message formatting preservation, rate limits, or behavior across different chat types.

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 two sentences, front-loaded with the verb and resource, and contains no extraneous information. Every word earns its place.

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?

Given the tool has 6 parameters, no output schema, and no annotations, the description is insufficient. It does not explain return values, error conditions, topic forwarding (message_thread_id), or protection features, leaving significant gaps for an AI 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 6 parameters have descriptions in the schema (100% coverage), so the description adds only minor value by explaining the default for chat_id. It does not elaborate on parameter constraints, formats, or interdependencies beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (forward a message) and the resource (from one chat to another), and mentions the default behavior when chat_id is omitted. However, it does not differentiate from the sibling tool 'forward_messages' which forwards multiple messages, so clarity is slightly diminished.

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

Usage Guidelines2/5

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

The description provides a conditional usage hint (omit chat_id to use default log group), but it does not specify when to use this tool over alternatives like copy_message or forward_messages, nor does it mention prerequisites or forbidden contexts.

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