Skip to main content
Glama

转发一条消息到别的会话

feishu_forward

Forwards an existing Feishu message unchanged to another chat or person, preserving cards, images, and files so results or user-sent content reach the right recipient without rewriting.

Instructions

把某条消息原样转发到另一个群或某个人(不经过改写,卡片/图片/文件都保持原样)。适合:把结果同步给另一个群、把用户发的图转给负责人。

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>",
      "to": "<to>"
    },
    "name": "feishu_forward"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes转发目标:chat_id(oc_)或 open_id(ou_)。
to_typeNo目标类型,默认 chat_id。
message_idYes要转发的消息 id(om_ 开头)。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true), the description discloses that the message is forwarded verbatim without rewriting and that card/image/file types survive intact — meaningful behavioral context about what the call actually does to content. It does not mention any permission prerequisite (e.g., bot membership in the target chat) or failure behavior, which keeps it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, purpose and preservation semantics front-loaded, followed immediately by concrete use cases. No redundant restatement of the name or title.

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 three-parameter, no-output-schema tool this covers purpose and content-preservation behavior adequately, but leaves gaps an agent might need: the email target type is unmentioned and no prerequisite about the target conversation is given.

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 coverage is 100%, so the schema already documents message_id, to, and to_type. The description's '另一个群或某个人' loosely maps to chat_id/open_id targets but adds no syntax, defaults, or mention of the 'email' enum option beyond the schema.

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 pairs a specific verb (转发/forward) with a specific resource (某条消息, a single message) and clarifies the 'as-is' semantics including cards/images/files being preserved. It does not explicitly contrast itself with the sibling feishu_merge_forward, so an agent must infer that single-message forwarding differs from merge forwarding.

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 '适合:...' clause supplies two concrete scenarios (syncing results to another group, forwarding a user's image to a responsible person), which implies when to use it. There is no statement of when NOT to use it and no named alternative (e.g., merge_forward for multiple messages), leaving routing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.