Skip to main content
Glama

发一张信息卡

feishu_send_info_card

Sends structured label-and-value fields as a formatted Feishu card to a chat, open ID, or email; use it for status reports, project lists, and statistics.

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": {
      "title": "<title>",
      "fields": "<fields>"
    },
    "name": "feishu_send_info_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes卡片标题
fieldsYes要展示的键值对
footerNo卡片底部小字备注
targetNo发送目标:chat_id(oc_ 开头)/ open_id(ou_ 开头)/ 邮箱。不填用默认会话。

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false and openWorldHint=true, so the fact that this is a write. The description adds content-shape guidance but does not note that sending goes to a default conversation when no target is given, nor anything about delivery visibility. With annotations carrying the safety profile, a 3 is appropriate.

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 front-loaded sentences: the first defines what the tool does, the second gives fit and anti-fit. There is no redundant or filler text.

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 4-parameter send tool with full schema coverage and no output schema, the description covers purpose and routing sufficiently. The only gap is the relationship to feishu_send_card, which is not addressed in the description.

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?

The input schema has 100% description coverage, so title, fields, footer, and target are fully documented. The description adds no meaning about parameters beyond the structured schema, which matches the baseline for fully covered schemas.

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 specifies a distinct verb phrase ("render as a Feishu card and send") and the content type (label+value structured info), so the intent is immediately usable. It does not distinguish itself from the sibling feishu_send_card, which likely also sends a card, leaving that boundary unstated within the description.

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?

It gives concrete positive cases (status reports, project lists, statistics) and an explicit negative case with a named alternative: long text should use feishu_send_text. An agent can decide between these two tools from the description alone.

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