Skip to main content
Glama
Sign In
Telegram MCP

Telegram MCP

by Anonymouse8882
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

quote_sticker

Forward messages to QuotLyBot to generate a quote sticker. Supports multiple message IDs and optional download.

Instructions

把若干条消息转发给 @QuotLyBot，生成引用贴纸并返回结果。

注意：被转发的消息内容会发送到第三方 bot (QuotLyBot) 的服务器上渲染。

Args: chat: 源消息所在对话。 message_ids: 要做成贴纸的消息 ID（同一对话，可多条组成对话截图）。 download: True 则把生成的 .webp 下载到本地。 timeout_seconds: 等待 bot 回复的秒数。

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": {
      "chat": "<chat>",
      "message_ids": "<message_ids>"
    },
    "name": "quote_sticker"
  }
}

Input Schema

NameRequiredDescriptionDefault
chatYes
downloadNo
message_idsYes
timeout_secondsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Discloses that messages are sent to an external bot's server, and mentions download option and timeout parameter, which reveals key behavioral traits. No annotations exist, so description carries the burden and handles it well.

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?

Two clear paragraphs: main action then parameter list. Every sentence adds value, no redundancy. Efficient and front-loaded with the core purpose.

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?

Covers purpose, external dependency, parameters, and download behavior. An output schema exists, so the description need not explain return values. Almost complete, missing only usage guidelines.

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

Parameters5/5

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

With 0% schema description coverage, the description compensates fully by explaining each parameter: chat (source chat), message_ids (IDs to stickerize), download (download .webp if true), timeout_seconds (seconds to wait for reply). Adds significant meaning beyond the schema.

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 clearly states the tool's function: forwarding messages to @QuotLyBot to generate a quote sticker and return the result. The verb 'forward' and resource 'message' plus the specific bot name make the purpose explicit and distinct from siblings.

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 includes a warning that message content is sent to a third-party server, implying privacy awareness, but does not explicitly state when to use this tool over others or provide alternative approaches. Lacks clear usage context.

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