HAOps MCP Server

haops_react_to_message

Add or toggle an emoji reaction on a discussion message to express feedback or sentiment.

Instructions

Add or toggle an emoji reaction on a discussion message.

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": {
      "projectSlug": "<projectSlug>",
      "discussionId": "<discussionId>",
      "messageId": "<messageId>",
      "emoji": "<emoji>"
    },
    "name": "haops_react_to_message"
  }
}

Input Schema

Name	Required	Description
`emoji`	Yes	Emoji to react with (e.g. "👍", "🎉")
`verbose`	No	If true, return the full API response instead of the compact summary (default: false)
`messageId`	Yes	UUID of the message to react to
`projectSlug`	Yes	The project slug (URL identifier)
`discussionId`	Yes	UUID of the discussion

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.8.0Jul 7, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It only mentions 'add or toggle' without clarifying whether toggling removes an existing reaction, idempotency, required permissions, rate limits, or response behavior (though the schema has a verbose param). The description is insufficient for safe invocation.

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?

The description is a single concise sentence, which is efficient. However, it omits important behavioral details, so while concise, it under-delivers for the necessary information.

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

Completeness2/5

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

Given no output schema and no annotations, the description should explain thoroughly. It fails to cover toggle semantics, error conditions, return value structure, or prerequisites (like needing discussion and message existence). The tool has 5 parameters but the description only hints at one.

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 baseline is 3. The description does not add any meaning beyond the schema descriptions. It mentions 'emoji' generally but does not elaborate on the other four parameters or their relationships.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the action ('Add or toggle an emoji reaction') and the target resource ('discussion message'). It distinguishes itself from sibling tools like haops_post_message, haops_edit_message, and haops_pin_message by specifying a unique reaction-focused operation.

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

Usage Guidelines3/5

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

The description implies usage for reacting to messages but does not explicitly state when to use this tool versus alternatives or provide context for when not to use it. No exclusions or comparisons to other reaction-related tools are given.

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

Deploy Server