Skip to main content
Glama

forward_group_single_msg

Forward a single QQ message to a group using a valid message_id from a message event or send result; the message must exist in the current account's store.

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>",
      "group_id": "<group_id>"
    },
    "name": "forward_group_single_msg"
  }
}

Input Schema

NameRequiredDescriptionDefault
group_idYes
message_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, destructiveHint=false, so safety profile is covered; the description adds beyond that by disclosing a data-availability precondition (the message must exist in the current account's store) and the non-obvious fact that negative message_id values are legitimate. It stops short of stating permission requirements or what happens on failure, but the added context is meaningful.

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 sentence with the action front-loaded and three supporting clauses, each of which adds a distinct constraint. No filler, though the clause chain is slightly dense and could be split for readability.

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 two-required-parameter mutation with no output schema, the description covers the non-obvious parts an agent needs: where message_id comes from, negative-value legality, and the store precondition. It lacks failure behavior and permissions, but nothing essential to a correct call is missing.

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

Parameters4/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 the load, and it does for the critical parameter: message_id must come from a message event or send result, may be negative, and must be resolvable in the local store. group_id is only implied by 'to a group' and gets no explicit semantics, which is the one gap.

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 states a specific verb+resource+target: forward a single message into a group. That implicitly separates it from the friend-forwarding sibling, but no sibling is named, so an agent still has to infer the routing between forward_group_single_msg and forward_friend_single_msg.

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 real input-provenance guidance ('use the real message_id from message events or send results') and a validity condition (must be queryable in the account's message store), which is genuinely useful. However, it never says when to choose this over batch/forward-组合 alternatives like send_group_forward_msg or the friend variant, so alternative selection is left implicit.

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