Skip to main content
Glama

发一条纯文本

feishu_send_text

Sends a plain-text message to a specified Feishu chat, user, or email for short conclusions, quick confirmations, and temporary replies. Use it for brief notes; switch to cards for long or formatted content.

Instructions

往指定会话发一条纯文本消息。适合短结论、一句话提示、快速确认、临时回复。不适合:超过约 30 行的长内容、需要排版/表格/多段落层级的内容 —— 那些改用 feishu_send_card(卡片能分块、加分隔线、加备注,可读得多)。也不适合需要后续原地刷新的场景:文本发出去就改不了,要更新请用卡片 + feishu_update_card。

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

Input Schema

NameRequiredDescriptionDefault
textYes消息正文,纯文本。支持换行,但不支持 markdown 渲染(会被原样当字面量显示)。
targetNo发送目标:chat_id(oc_ 开头)/ open_id(ou_ 开头)/ 邮箱。不填则发到默认会话(需已配置 FEISHU_DEFAULT_CHAT_ID,否则会报错)。

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 declare readOnlyHint=false and openWorldHint=true, so the description must carry the behavioral load — and it does, disclosing that sent text is immutable ("文本发出去就改不了") and that markdown is not rendered. It stops short of stating permission scopes or failure modes for an invalid target.

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?

Front-loads the purpose, then the use cases, then the exclusions with alternatives — a clean decision order. Slightly repetitive in restating the card alternative twice, but no sentence is wasted.

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-parameter send tool with no output schema, the description covers the immutability constraint, the formatting limitation, and the sibling alternatives. The remaining gap is error/permission behavior (invalid target, missing default chat), which the schema partially covers.

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 both text and target are already fully documented, including the oc_/ou_ prefix convention and the default-chat fallback. The description adds no parameter meaning beyond that, which is the expected baseline when the schema does the work.

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?

States a specific verb and resource ("往指定会话发一条纯文本消息") and immediately differentiates itself from feishu_send_card and feishu_update_card by capability, so an agent can route without opening any schema.

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 explicit positive cases (short conclusions, one-line prompts, quick confirmations, temporary replies) and explicit negative cases (over ~30 lines, content needing layout/tables/multi-level paragraphs), each paired with the sibling to use instead. The in-place-refresh exclusion with a named alternative is exactly the guidance an agent needs.

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