Skip to main content
Glama

Add a chat reaction

chat_react
Idempotent

Adds an emoji reaction to a flat chat message by message ID, accepting one emoji per call. Use it to respond to messages without changing or posting text.

Instructions

Adds your emoji reaction to any message in the flat chat; you can add several different emojis to one message. Each member holds a given emoji at most once per message, so an emoji you already set stays as it is. Does not change or post message text. Returns ok. Only a single emoji (one pictograph, flag or keycap, with skin-tone or joiner sequences counting as one) is accepted, otherwise emoji_invalid; an unknown message gives message_not_found and a deleted one 409 message_deleted. To take a reaction back use chat_unreact; to write a message use chat_send.

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": {
      "id": "<id>",
      "emoji": "<emoji>"
    },
    "name": "chat_react"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesId of the message to react to, from chat_messages.
emojiYesThe reaction: one emoji, sent as the emoji character itself, not a name or shortcode like :thumbsup:. Pass the same string to chat_unreact to remove it.
wgCodeNoShare code of the flat (code from wg_list). Leave it out when the account belongs to one flat.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • addedInput schema / properties / emoji / description
      Added value: +"The reaction: one emoji, sent as the emoji character itself, not a name or shortcode like :thumbsup:. Pass the same string to chat_unreact to remove it."
    • addedInput schema / properties / id / description
      Added value: +"Id of the message to react to, from chat_messages."
  2. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false; the description operationalizes idempotency ("an emoji you already set stays as it is") and states the success return ("Returns ok") plus three concrete failure modes. That is behavior an agent needs for retry and error handling, none of which is derivable from the annotations alone.

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?

Front-loaded with the action, then semantics, then error codes, then sibling routing – a sensible order. The emoji-validity parenthetical is dense but load-bearing; the only mild cost is that the sentence carrying it is long enough to slow scanning.

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 and the error surface, and it documents the idempotent no-op case. Nothing an agent needs to invoke this three-parameter mutation correctly is missing.

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?

Schema coverage is 100%, so the baseline would be 3, but the description adds real meaning beyond it: the one-pictograph rule with skin-tone and joiner sequences counted as a single emoji, the emoji_invalid rejection, the message_not_found and 409 message_deleted outcomes, and the per-member-once semantics. This is constraint information the schema's maxLength of 16 cannot convey.

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?

"Adds your emoji reaction to any message in the flat chat" gives a specific verb (adds) and resource (emoji reaction on a message), and the closing sentence explicitly names what this tool is not: chat_unreact for removal, chat_send for writing. An agent can separate it from every listed sibling without opening a schema.

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?

Names the alternatives and the condition that selects them ("To take a reaction back use chat_unreact; to write a message use chat_send"), and adds a negative boundary ("Does not change or post message text"). Both when-to-use and when-not-to-use are stated rather than inferred.

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