Skip to main content
Glama

get_forward_msg

Read-only

Fetch merged forward message nodes by resource ID or message ID to inspect embedded content and reuse quoted nodes when sending.

Instructions

获取合并转发消息(id 或 message_id) id 是合并转发资源标识,通常来自转发消息段或上传结果 res_id,不是普通数值 message_id。 Returns: { messages }:转发内的消息节点数组(每项为 OneBot 消息事件);reply 保留 id,有内嵌引用内容时附带 message 和可用的 qq/time/seq,可作为转发节点 content 再次发送。

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": "get_forward_msg"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
message_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuine value, explaining the returned { messages } structure, that each item is a OneBot message event, and that reply nodes retain id plus embedded message/qq/time/seq. The lower end of the range applies because error behavior (unknown id) is not disclosed.

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?

It leads with the purpose, then the identifier caveat, then the return contract, which is an effective order. The return clause is dense but every part (messages array shape, reply id retention, re-send usage) is operational information, not filler.

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?

No output schema exists, so the description correctly absorbs the return-value explanation and covers the tricky id/message_id distinction. For a two-parameter read tool with annotations, the only real gaps are error semantics and argument precedence.

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 all parameter meaning. It compensates well for id by naming its origin (forward segment or upload res_id) and warning that it is not an ordinary numeric message_id, but it leaves message_id only implied, and it does not say what happens when both are supplied or when neither is (required=0).

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?

It uses a specific verb+resource: 获取合并转发消息, and it identifies which argument holds which identifier (id = forward-resource identifier, not a plain numeric message_id). That description is clear enough to act on. It does not compare itself with sibling readers such as get_msg, so the agent has no explicit note on when to use this tool rather than a generic message getter.

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 parametric guidance (id comes from a forward message segment or the res_id of an upload result) implies the read-the-forward use case, and the final clause hints that the tool can be used when you want to re-send nodes. But it never states when to use this tool rather than get_msg or how to handle a failed lookup; the agent must infer that from the name.

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