Skip to main content
Glama

send_forward_msg

Sends merged forward messages to QQ groups or users, routing by message type and target ID; without a target, it only uploads resources and returns message_id 0.

Instructions

发送合并转发(按 message_type/群号自动路由) 替换目标群号;nodes 是自定义转发节点数组。send_forward_msg 不提供目标时仅上传资源并返回 message_id=0。 Returns: { message_id, res_id, forward_id }

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "send_forward_msg"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior4/5

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

Annotations only declare readOnly=false, destructive=false, openWorld=true; the description adds genuine behavior beyond them — automatic routing by message_type/group_id, the degenerate no-target mode that only uploads and returns message_id=0, and the reply.data.message override for quote previews inside nodes. It stops short of disclosing permission/rate-limit or failure behavior for a send operation.

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?

Short and roughly front-loaded, but the structure is loose: Chinese prose, an English 'Returns:' suffix, and a reference to a nonexistent parameter all in three sentences. Nothing is padding, but the mixed framing and phantom parameter make it harder to parse than its length justifies.

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 9-parameter mutation tool with zero required parameters and 22% schema coverage, the description leaves most of the surface unexplained — including how 'message' vs 'messages' differ and what news/source/prompt/summary do. It does list the return keys, which partly offsets the missing output schema, but the input contract remains largely undocumented.

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 only 22% across 9 parameters, and the description does not compensate: news, prompt, source, summary, user_id, message_type and group_id get no explanation beyond a passing '替换目标群号'. It also misnames the node array as 'nodes', while the schema exposes both 'message' and 'messages' — an ambiguity the description does nothing to resolve.

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+resource (发送合并转发 / send a merged forward) and explains the routing rule (按 message_type/群号自动路由), which implicitly separates it from the near-identical siblings send_group_forward_msg and send_private_forward_msg. It is weakened by referring to a 'nodes' parameter that does not exist in the schema (the actual properties are 'message'/'messages'), which muddies rather than clarifies the resource model.

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 routing note implies when to prefer this generic dispatcher over the group/private-specific siblings, and the no-target case is described ('不提供目标时仅上传资源并返回 message_id=0'). However, there is no explicit 'use X instead when Y' statement and no statement of prerequisites for choosing a channel.

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