Send a Feishu group chat share card to a target group. Provide the source group's open_chat_id to deliver a clickable card that lets recipients access the shared chat.
向飞书群发送群名片分享卡片。
| Name | Required | Description | Default |
|---|---|---|---|
| shareChatId | Yes | 被分享群的 open_chat_id（形如 oc_xxxxx） |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only says 'send', implying a side effect, but does not mention permissions, reversibility, error conditions, or the nature of the sent card. This is a significant gap for a mutation tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence with zero waste. It front-loads the primary action and leaves nothing extraneous.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no annotations and no output schema, the description is minimal. It fails to explain prerequisites (e.g., group existence), potential errors, or what the recipient sees. For a side-effectful action, this is inadequate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, with the parameter shareChatId clearly described as the open_chat_id of the shared group. The description adds no additional meaning beyond the schema, so a baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Send a group business card sharing card to a Feishu group' states a specific verb and resource (group card). It is distinguishable from siblings like send_text or send_image because it targets a specific content type, though it doesn't explicitly name alternatives.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The usage is implied: use this when you need to share a group card. There is no explicit guidance on when to choose this over other send_* tools, and no exclusions or prerequisites are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.