Skip to main content
Glama
Sign In
HomarUScc

HomarUScc

by kcdjmaxx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

telegram_react

React to Telegram messages with an emoji to acknowledge quickly without sending a full reply.

Instructions

React to a Telegram message with an emoji. Use for lightweight acknowledgment instead of sending a full reply.

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": {
      "chatId": "<chatId>",
      "messageId": "<messageId>",
      "emoji": "<emoji>"
    },
    "name": "telegram_react"
  }
}

Input Schema

NameRequiredDescriptionDefault
emojiYesEmoji to react with (e.g. 👍, ❤️, 🔥, 😂, 🤔, 👎)
chatIdYesTelegram chat ID
messageIdYesMessage ID to react to

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.3/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It only states the primary action and intended use case, but does not discuss potential side effects (e.g., replacing existing reactions), error handling, or permission/rate-limit considerations. It is adequate for a simple tool but leaves these gaps.

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 a single, front-loaded sentence that immediately states the action, followed by a short usage note. Every word earns its place with no redundancy or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with fully described parameters and no output schema, the description provides sufficient context: what it does, when to use it, and how it differs from alternatives. The low complexity means no additional context is necessary.

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 100%, so the schema already documents all three parameters (chatId, messageId, emoji) with examples for the emoji. The description does not add additional parameter-level meaning beyond what the schema provides, so the baseline score of 3 is appropriate.

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 action ('React to a Telegram message with an emoji') and resource, and explicitly distinguishes itself from sending a full reply, thus differentiating from sibling tools like telegram_send.

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

Usage Guidelines5/5

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

The description explicitly indicates when to use the tool ('Use for lightweight acknowledgment') and provides an alternative to avoid ('instead of sending a full reply'), guiding tool selection among Telegram siblings.

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