Skip to main content
Glama

React to chat message

react_to_chat_message

Put an emoji on a chat message, or take yours off, as yourself — as pressing it under the message on the screen does: one emoji ('👍', '🎉', any single emoji), on (the default) or off ('remove' true), said outright so a repeat changes nothing. The chat's open screens show it at once; nobody is notified, and no unread count moves. Anybody who may write in the chat may react; not on a deleted message, and not in a secret chat, which has no reactions. At most 10 of yours on one message. Answers with the message's reactions after it.

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": "react_to_chat_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
emojiYesOne emoji, e.g. '👍'.
chatIdYesThe chat's id.
removeNoTrue takes your emoji off.
messageIdYesThe message's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnly=false, destructive=false, openWorld=false), it discloses that other screens update at once, no notifications fire, no unread count moves, repeats are no-ops, a 10-reaction cap applies, and it returns the message's reactions afterwards. These are exactly the side-effect details annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and the add/remove semantics are front-loaded, and the remaining sentences are dense with constraints rather than filler. The parenthetical 'as pressing it under the message on the screen does' is illustrative padding that could be trimmed.

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?

With no output schema, the description compensates by stating the return value ('answers with the message's reactions'), and it covers permissions, limits, and visibility effects for a mutating tool. Nothing an agent needs to call it correctly appears to be missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3; the description adds real meaning by tying 'remove' true to the off action, stressing a single emoji, and explaining that the default is to add. It does not clarify chatId/messageId beyond the schema, but those are self-evident.

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 opens with a specific verb+resource ('Put an emoji on a chat message, or take yours off') and immediately scopes it as acting 'as yourself', which distinguishes it from sibling message tools like edit_chat_message, delete_chat_message, and send_chat_message.

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 concrete when/when-not conditions: only where the user may write, not on a deleted message, not in secret chats, max 10 of your own per message, and 'remove' true to take it off. It never names a sibling alternative explicitly, which keeps it short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources