Skip to main content
Glama

send_group_forward_msg

Sends a merged forward message to a specified QQ group using custom forwarding nodes, returning message, resource, and forward IDs.

Instructions

发送群合并转发 替换目标群号;nodes 是自定义转发节点数组。send_forward_msg 不提供目标时仅上传资源并返回 message_id=0。 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": {
      "group_id": "<group_id>"
    },
    "name": "send_group_forward_msg"
  }
}

Input Schema

NameRequiredDescriptionDefault
newsNo
promptNo
sourceNo
messageNo转发节点数组;节点 content 内的 reply.data.message 可提供自定义引用内容(字符串或消息段),qq/time/seq 可选;仅用于转发内引用预览。
summaryNo
group_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 and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond them: the exact return shape { message_id, res_id, forward_id } and the fact that a no-target send returns message_id=0. It says nothing about side effects, permissions needed to send into a group, or rate limiting.

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?

It is short, but the structure is choppy: semicolon-separated fragments, an embedded digression about a sibling tool, and a trailing 'Returns:' clause. Nothing is padded, yet the pieces are not ordered for an agent's first read.

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?

Seven parameters with no output schema and only partial schema descriptions leave significant gaps: four params (news, prompt, source, summary) have zero explanation anywhere, and the required group_id is only glossed as '群号'. For a mutation tool that posts content into a group, this is thin even accounting for the annotation coverage.

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 43%, so the description needs to carry weight, and it largely does not: news, prompt, source, summary, and the difference between message and messages are never explained. The one real addition is that group_id is the group to replace/target. Worse, it introduces a parameter name ('nodes') that does not exist in the schema, which can mislead an agent filling arguments.

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 ('发送群合并转发' – send a merged forward to a group) and distinguishes itself from plain single-message forwarding via '合并转发'. It also highlights the group-target substitution. It loses a point because it explains the tool partly through a sibling ('send_forward_msg') and refers to 'nodes' while the schema calls the field message/messages, creating a naming mismatch.

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 only implied: '合并转发' tells an agent this is the merged/multi-node variant, and the note about send_forward_msg without a target clarifies a related tool's fallback mode. There is no explicit statement of when to pick this over send_private_forward_msg, forward_group_single_msg, or send_forward_msg for group targets.

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