Skip to main content
Glama

forward_friend_single_msg

Forward a single message to a QQ friend using a real message_id from an event or send result; ensure the message is queryable in the current account's message 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>",
      "user_id": "<user_id>"
    },
    "name": "forward_friend_single_msg"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_idYes
message_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the agent knows this mutates external state. The description adds real value beyond that by stating the message must exist in the account's message store and that negative message_ids are legal — a non-obvious edge case the schema's `not: {const: 0}` hint alone would not clarify. It still does not say what happens on failure (error vs partial forward) or whether the forward appears in the friend conversation immediately.

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?

One compact sentence with semicolon-separated clauses: action first, then id sourcing, then the negative-value rule, then the storage precondition. Nothing is redundant, though the punctuation-dense run-on makes the constraints easy to skim past.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter write tool with no output schema, the description covers the main failure mode (id not resolvable / not in store) and one surprising edge case. It is still thin on the required user_id semantics and on post-call behavior, which matters because the tool is openWorld and non-read-only.

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 0%, so the description must carry parameter meaning, and it does well for message_id (source of the id, negative values valid, must be retrievable from the store). It says nothing about user_id beyond it being a required target — the agent must infer it is the recipient friend's identifier rather than, e.g., a message sender. Half the parameters are therefore unelaborated.

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 has a specific verb plus resource plus destination: "转发单条消息给好友" (forward a single message to a friend). It implicitly distinguishes itself from the group variant forward_group_single_msg, but never names the sibling explicitly, so differentiation requires the reader to notice the friend/group contrast.

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 supplies precondition guidance (the message_id must come from a message event or send result, and the message must be queryable in the current account's store) which steers correct usage. However, it gives no explicit when-to-use or when-not-to-use guidance and never routes the agent to an alternative such as forward_group_single_msg or send_forward_msg, so usage is only implied.

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