Skip to main content
Glama
Sign In
AdsMCP

AdsMCP

by skynes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ads_telegram_chat_reply

Sends one explicitly confirmed public reply to a specific accessible Telegram group message when the message contains a relevant explicit request and group rules permit it.

Instructions

Reply publicly to one message inside an accessible Telegram group when the message contains a relevant explicit request and the resource rules permit it. Requires Telegram Premium and explicit confirm=true; reports a read-only unread-human-dialog preflight without blocking the write; never sends a private message and never bypasses moderation, CAPTCHA or guest-send restrictions.

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_id": "<message_id>",
      "text": "<text>",
      "confirm": "<confirm>"
    },
    "name": "ads_telegram_chat_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
chatYes@username or t.me public group
textYes
confirmYesExplicitly confirm sending this one public group reply
message_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral burden and does so well: it discloses the Telegram Premium requirement, mandatory confirm=true, the non-blocking read-only unread-human-dialog preflight, and several hard restrictions. It stops short of describing failure behavior or rate limits, but the key mutation semantics are clear.

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 dense but front-loaded: the action and scope come first, followed by requirements and restrictions. Every clause adds operational meaning with no filler.

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 mutation tool with no annotations and no output schema, the description covers the important context an agent needs: access requirements, confirmation, preflight behavior, and public-only restrictions. Remaining gaps around failure handling and exact response semantics are minor given the available schema.

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?

Schema coverage is 50%, so the schema already documents chat and confirm. The description reinforces the public-group scope and explicit confirmation requirement, but it adds little detail for text or message_id beyond implying a single target message.

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 a specific verb and resource: reply publicly to one message inside an accessible Telegram group. It also scopes the action away from private messaging and clarifies that the target is a group message rather than a channel or general send operation.

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?

It gives explicit conditions for use: the message must contain a relevant explicit request and resource rules must permit it, and Telegram Premium plus confirm=true are required. It also states exclusions such as never sending a private message and never bypassing moderation or CAPTCHA, though it does not name alternative sibling tools.

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