Skip to main content
Glama

Remove a chat reaction

chat_unreact
Idempotent

Removes your own emoji reaction from a message without affecting other members' reactions; repeating the call is safe if the reaction is already gone.

Instructions

Removes your own emoji reaction from a message; other members' reactions stay. Removing a reaction you never set changes nothing, so repeating the call is safe. An unknown message gives message_not_found and a deleted one 409 message_deleted. To add a reaction use chat_react.

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_unreact"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesId of the message the reaction is on, from chat_messages.
emojiYesThe emoji of your reaction to remove, exactly as it was added with chat_react.
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 emoji of your reaction to remove, exactly as it was added with chat_react."
    • addedInput schema / properties / id / description
      Added value: +"Id of the message the reaction is on, from chat_messages."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations by explaining the underlying semantics of idempotency ('removing a reaction you never set changes nothing'), the scope of the mutation (only your own reaction is affected), and concrete failure behavior — message_not_found for an unknown message and 409 message_deleted for a deleted one. This is exactly the context an agent needs to decide whether to retry.

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?

Three tight sentences: mutation scope first, idempotency second, error behavior third, sibling pointer last. Every sentence carries distinct information and nothing is repeated from the schema.

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 three-parameter mutation with no output schema, the definition covers outcome, scope, idempotency, and the error cases that matter. Nothing an agent needs in order to call this correctly or interpret failure is missing.

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 description coverage is 100%, so the schema already documents id, emoji, and wgCode in detail. The description adds no parameter-level meaning beyond that — it never mentions wgCode or the emoji matching requirement itself — so the baseline of 3 for a fully-documented schema 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?

Specific verb ('Removes') plus resource ('your own emoji reaction from a message') with an explicit scope limit — only your own reaction, other members' stay. The final sentence names the inverse sibling chat_react, so the agent can separate the two without reading either schema.

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?

Clear context for when this applies and an explicit alternative ('To add a reaction use chat_react'), plus a useful note that repeated calls are safe. It stops short of enumerating when-not scenarios (e.g. removing another member's reaction simply isn't possible, which is only implied by 'other members' reactions stay').

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