Skip to main content
Glama

引用回复某条消息

feishu_reply

Sends a plain-text quote reply to a specific Feishu message so conversations retain the original context and avoid ambiguity in busy group chats.

Instructions

在会话里对某条消息做引用回复(飞书会把它挂在原消息下面)。适合:用户点名提问、需要保留"回的是哪一条"的上下文、在刷屏群里避免歧义。不适合:只是想发一条新消息(用 feishu_send_text);需要排版或要后续刷新(用卡片相关工具,回复接口只发纯文本)。

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>",
      "text": "<text>"
    },
    "name": "feishu_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes回复正文,纯文本。
message_idYes被回复的那条消息 id(om_ 开头)。注意这是"原消息",不是回复本身。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only say readOnly=false and openWorld=true; the description adds the key behavioral fact that the reply is plain-text only and gets attached beneath the original message, plus that card tools are required for formatting/refreshable content. It doesn't cover failure modes (invalid/deleted message_id) or permission requirements, so it falls short of 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.

Conciseness4/5

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

The core action is front-loaded and the 适合/不适合 split is easy to scan. Slightly wordy with the quoted parenthetical, but every clause carries routing or constraint information.

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 2-parameter write tool with full schema coverage and no output schema, the description covers purpose, threading behavior, content-type limits, and alternatives. It omits what the call returns and how errors on a bad message_id surface, which an agent would still want.

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% and the schema already explains that message_id is the om_-prefixed original message, not the reply. The description adds no parameter-level detail beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb+resource: 引用回复 (quote-reply) to a specific message, and states the resulting behavior (Feishu threads it under the original). It is clearly distinguishable from feishu_send_text and the card tools, which are named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives both positive conditions (user asks a pointed question, need to preserve 'which message this answers', avoid ambiguity in busy groups) and negative ones (just send a new message → feishu_send_text; need formatting or later refresh → card tools). Alternatives are named with the condition that selects them.

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