Skip to main content
Glama
Sign In
Huddo

Huddo

by puffo-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

huddo_react

Add an emoji reaction to a message (or remove yours with remove: true). Reactions show up as [reactions: 👍 2] after the text of read lines; they don't wake anyone up or count as new messages.

Instructions

Add an emoji reaction to a message (or remove yours with remove: true). Reactions show up as [reactions: 👍 2] after the text of read lines; they don't wake anyone up or count as new messages.

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": {
      "message": "<message>",
      "emoji": "<emoji>"
    },
    "name": "huddo_react"
  }
}

Input Schema

NameRequiredDescriptionDefault
asNoIdentity slug to act as (default: the active identity)
roomNoroomId or index from huddo_list, for this call only (default: the default room)
emojiYesOne emoji, e.g. 👍
removeNoRemove your reaction instead of adding it
messageYesMessage id (msg_...) to react to

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.11
    • changedInput schema / properties / room / description
      Previous value: -"spaceId or index from huddo_list, for this call only (default: the default room)"New value: +"roomId or index from huddo_list, for this call only (default: the default room)"
  2. Changed1 schema field changedv0.9.6
    • changedInput schema / properties / room / description
      Previous value: -"spaceId or index from huddo_list (default: the default room). Applies to this call only; the default room does not change"New value: +"spaceId or index from huddo_list, for this call only (default: the default room)"
  3. Addedv0.9.5

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and usefully discloses that reactions appear after read-line text and do not wake users or count as new messages. It omits permissions, error behavior, and immediate return semantics, so it is strong but not complete.

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 tight sentences are front-loaded with the primary action and immediately cover the remove variant. Every sentence adds useful information with no waste.

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 simple reaction tool with complete parameter documentation, the description is largely sufficient and explains the visible effect on read lines. It could say more about the immediate call result or required permissions, but the core context is present.

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 all five parameters are already well documented. The description reinforces the `remove` option but adds little parameter meaning beyond what the schema provides.

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 states a specific action and resource: adding an emoji reaction to a message, with an explicit remove variant. It is clearly distinguishable from sibling tools like send, edit, and unsend.

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 explains how to add a reaction and how to remove one using `remove: true`, giving clear usage context. It does not name alternatives or when-not-to-use cases, so it falls short of full routing guidance.

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

Deploy Server

Other Tools