Skip to main content
Glama

React to a message

react
Idempotent

Add or remove an emoji reaction on a chat message; the reaction is visible to everyone, so confirm with the user before acting.

Instructions

Add an emoji reaction to a message (or remove one with remove: true). Everyone in the chat sees it, so it acts on the user's behalf: confirm with the user first.

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>",
      "reaction": "<reaction>"
    },
    "name": "react"
  }
}

Input Schema

NameRequiredDescriptionDefault
chatIDYesChat ID (or local chat ID)
removeNoRemove this reaction instead of adding it (default false)
reactionYesThe emoji, e.g. 👍
messageIDYesID of the message to react to

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, idempotent, open-world behavior, so the bar is lower; the description still adds meaningful context by disclosing social visibility ('everyone in the chat sees it') and the confirmation requirement. It does not cover edge cases such as reacting twice with the same emoji or what an invalid emoji returns.

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 compact sentences with zero filler; the primary operation is front-loaded and the removal variant and confirmation caveat follow in priority order.

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 four-parameter tool with no output schema and annotations covering the safety profile, the description supplies the key operational context: visibility, user-impersonation, and the confirmation step. Only minor gaps remain, such as notification behavior or how removal interacts with idempotency.

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 chatID, messageID, reaction, and remove, including the default for remove. The description only restates the remove toggle and adds no format or constraint detail beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource (add an emoji reaction to a message) and covers the inverse operation (remove with remove: true) in the same breath. It is clearly distinguishable from siblings like get_reactions or delete_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?

Gives an explicit precondition: it acts on the user's behalf and is visible to everyone, so confirm with the user first. That is real when-to-use guidance, though it does not name alternatives (e.g., reading existing reactions via get_reactions) or when not to react.

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