Skip to main content
Glama
Sign In
telegram-mcp

telegram-mcp

by resccrew
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

forward_messages

Forward specific messages from one chat to another by specifying source chat, destination chat, and message IDs.

Instructions

Forward messages from one chat to another.

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": "<from_chat>",
      "message_ids": "<message_ids>",
      "to_chat": "<to_chat>"
    },
    "name": "forward_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
to_chatYes
from_chatYes
message_idsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description must disclose side effects and constraints. It conveys the basic forward action but does not state whether original messages are left intact, whether permissions are needed, what happens on invalid message_ids, or any rate-limit/auth considerations.

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 short, front-loaded sentence states the core operation with no filler or redundant repetition of the tool name. It is easy to parse and wastes no words.

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?

Although an output schema exists, the description lacks behavioral, usage, and parameter context that an agent needs to invoke the tool confidently. A simple operation, but absent any annotation support it is too sparse to be considered complete.

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

Parameters2/5

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

Schema description coverage is 0%, so the description should clarify parameters. It broadly maps 'from one chat' to from_chat, 'another' to to_chat, and 'messages' to message_ids, but it does not define expected ID formats, the relationship between message_ids and from_chat, or ordering/duplication behavior.

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 uses a specific verb ('Forward') with a clear resource ('messages') and a directional relationship ('from one chat to another'). This distinguishes it from siblings like send_message or delete_messages, making the tool's purpose immediately unambiguous.

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?

No guidance is given about when to choose forwarding over send_message or other message operations, and no exclusions or prerequisites are stated. The usage context is left entirely to inference from the tool name.

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