Skip to main content
Glama

forward_messages

Forward existing QQ messages by ID to a friend or group, bundled as one merged card or sent individually.

Instructions

Forward existing messages (by message_id) to a friend or group — as one 合并转发 bundle (default) or one by one.

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": {
      "target": "<target>",
      "message_ids": "<message_ids>"
    },
    "name": "forward_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
mergedNoBundle into one 合并转发 card
targetYesWho to talk to: "qq:<QQ号>" for a friend/private chat, "group:<群号>" for a group, a bare number, or a friend remark/nickname/group name (must be unambiguous).
message_idsYesmessage_ids to forward, in order

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, open-world write, so safety is covered elsewhere. The description adds the meaningful behavioral detail that the default is a single 合并转发 card versus sending items individually, but it says nothing about failure behavior for missing/expired message_ids, ambiguous targets, or ordering guarantees.

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 front-loaded sentence with no filler: verb, input, destination and mode all appear immediately. The em-dash clause carrying the two modes is efficient, though the untranslated 合并转发 term assumes domain familiarity.

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 forward tool with full schema coverage, complete annotations and no output schema, the description covers the essential decisions (target, mode). Only failure/error semantics and sibling routing are absent, which is a modest gap rather than a blocking 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 description coverage is 100%, so target formats, merged semantics and message_id ordering are already fully documented in the schema. The description restates the merged default and the by-id nature of the input without adding syntax or edge-case meaning beyond the structured fields, which is the baseline case.

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 gives a specific verb ('Forward') plus resource ('existing messages by message_id') and states the two supported destinations (friend or group) and two output modes (merged bundle vs one by one). This implicitly separates it from the single-destination siblings (forward_friend_single_msg, forward_group_single_msg), but it never names an alternative explicitly.

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?

Usage is implied: use it when you already have message_ids and want to re-deliver them to a friend or group, with merged mode as the default. There is no explicit when-not guidance, no mention of prerequisites such as the messages still existing or being accessible, and no routing hint toward the sibling single-target forward tools.

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