Skip to main content
Glama

send_private_forward_msg

Send merged forward messages in a private QQ chat to a specified friend by user ID, with optional summary, source, and forwarding nodes.

Instructions

发送私聊合并转发 替换目标好友 QQ 号。 Returns: { message_id, res_id, forward_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": {
      "user_id": "<user_id>"
    },
    "name": "send_private_forward_msg"
  }
}

Input Schema

NameRequiredDescriptionDefault
newsNo
promptNo
sourceNo
messageNo转发节点数组;节点 content 内的 reply.data.message 可提供自定义引用内容(字符串或消息段),qq/time/seq 可选;仅用于转发内引用预览。
summaryNo
user_idYes
messagesNo转发节点数组;节点 content 内的 reply.data.message 可提供自定义引用内容(字符串或消息段),qq/time/seq 可选;仅用于转发内引用预览。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, destructiveHint=false, so the write/open-world nature is covered structurally. The description usefully discloses the return shape { message_id, res_id, forward_id } in the absence of an output schema, which is real added value, but it says nothing about failure modes, permissions, or what "替换目标好友 QQ 号" actually changes on the server.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short clauses with no padding, and the return values are stated compactly at the end. However, the sentence is cryptic and mixes Chinese and English awkwardly, with the target-replacement clause bolted on rather than structured as guidance.

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?

For a 7-parameter write tool with 29% schema coverage and no output schema, the description is thin: it covers the destination and return fields but leaves most of the payload parameters unexplained. An agent would not know how to construct the forward nodes or what news/prompt/source do from this definition alone.

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 coverage is only 29% across 7 parameters. The description only gestures at user_id (target friend QQ) and does not explain news, prompt, source, summary, or the relationship between message and messages, leaving most parameters undocumented in both schema and prose. It therefore fails to compensate for the low coverage.

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 specific verb and resource: sending a merged/combined forward message in a private chat. It implies the target is a friend's QQ number (user_id), which distinguishes it loosely from send_forward_msg / send_group_forward_msg, but it never states the private-vs-group distinction explicitly, so the differentiation is inferred rather than declared.

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 phrase "发送私聊合并转发" implies usage (private-chat merged forwards), giving a weak contextual cue. There is no explicit guidance on when to prefer this over send_forward_msg, send_fake_forward, or forward_friend_single_msg, and no prerequisites or exclusions are stated.

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