Skip to main content
Glama

set_group_reaction

Set or clear a reaction on a QQ group message using its real message ID. Use event or send-result message IDs; the message must exist in your account's message history.

Instructions

群聊表情回应 使用消息事件或发送结果中的真实 message_id,负值合法;消息须在当前账号的消息存储中可查询。

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_id": "<message_id>",
      "code": "<code>"
    },
    "name": "set_group_reaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes
is_setNo
group_idNo
message_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare a non-read-only, non-destructive, open-world mutation. The description adds real value beyond them by disclosing a data precondition (message must exist in local store) and that negative message ids are legal, but says nothing about toggling semantics, permissions, or rate limits.

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?

A single compact line, front-loaded with the purpose followed by the id-sourcing rule and the precondition. No filler, though the clauses are tightly packed with semicolons.

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

Completeness3/5

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

With no output schema and zero schema description coverage, the description covers the trickiest part (message_id validity) but leaves the emoji code, the is_set toggle, and group_id ambiguous. Adequate for a simple mutation, but not complete for a four-parameter tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry all four parameters. It only clarifies message_id (source, negative values allowed, reachability requirement); code, is_set (the default-true toggle) and group_id remain completely unexplained.

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 names a concrete verb and resource (group-chat emoji reaction) and the tool name reinforces it. It is distinguishable from set_msg_emoji_like only by the '群聊' scope word, not by any explicit differentiation.

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?

It gives an important precondition (the message must be queryable in the current account's message store) and where to source the id, which implies correct usage. It never states when to prefer this over a sibling like set_msg_emoji_like, nor any failure/exclusion conditions.

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