Skip to main content
Glama
Sign In
huly-mcp-selfhost

huly-mcp-selfhost

by JoKeks2023
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

add_reaction

Adds an emoji reaction to a message or comment; does nothing if the reaction already exists.

Instructions

Add your emoji reaction to a message or comment (no-op if already there); undo: remove_reaction

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": {
      "workspace": "<workspace>",
      "messageId": "<messageId>",
      "emoji": "<emoji>"
    },
    "name": "add_reaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
emojiYese.g. 👍
messageIdYesMessage id (list_messages, list_comments, list_thread)
workspaceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.5.1

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=false, and the description adds a genuinely useful behavioral fact beyond them: the call is idempotent ('no-op if already there'), so the agent knows repeat calls are harmless. It says nothing about who may react, whether reactions are visible to others, or what a success response contains, so the added context is real but thin.

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?

A single sentence with the primary action front-loaded, followed by the idempotency caveat and the inverse tool. No filler, and the parenthetical is load-bearing rather than decorative.

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 three-parameter, non-destructive mutation with no output schema, the description covers the essentials: what it acts on, that it is safe to repeat, and how to undo. The only missing piece is any note about the workspace parameter or required access, a minor gap at this complexity.

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 67%, and the schema itself gives an emoji example and lists the tools that produce messageId. The description adds one non-obvious point — the id can be a message or a comment — but leaves the 'workspace' parameter undocumented in both places. Baseline 3 is right when the schema does most of the work.

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 (add) plus the resource (emoji reaction) and the target set (a message or comment), which is exactly the distinction an agent needs. It also names the inverse operation, remove_reaction, so the tool is separable from its closest sibling without opening any 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?

The parenthetical 'undo: remove_reaction' explicitly routes the agent to the correct alternative when the goal is removal, which is the main ambiguity for a reaction tool. It does not discuss when a reaction is preferable to a comment reply or any permission preconditions, so context is clear but not exhaustive.

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