Skip to main content
Glama

把本地图片发进会话

feishu_send_image

Send local images as native Feishu chat image messages so recipients can preview thumbnails and open full-size views; use for screenshots, charts, or design previews.

Instructions

把本地图片以"图片消息"发到飞书会话,收到的人可以直接在聊天里看到缩略图、点开大图。只在需要预览时用;要发 PDF、压缩包、代码等非图片文件请用 feishu_send_file。支持 png / jpg / jpeg / gif / webp / bmp,单张上限 10MB。截图、图表、设计稿的效果图都适合走这条。

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": {
      "path": "<path>"
    },
    "name": "feishu_send_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes本地图片路径(绝对路径或相对路径,内部会 path.resolve)
targetNo发送目标:chat_id(oc_ 开头)/ open_id(ou_ 开头)/ 邮箱。不填用默认会话。
captionNo随图发的说明文字;非空时先发一条文本消息,再发图片

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.4/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 the delivery form (thumbnail in chat, click to expand), supported formats, and a 10MB size cap — useful operational constraints an agent cannot infer from structured fields. It does not say what happens on an oversized or unsupported file, which keeps it from 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?

Four short sentences, front-loaded with purpose, then the alternative routing, then format/limit constraints, then examples. No sentence is redundant or restates the name.

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 simple three-parameter send tool with a fully documented schema, the description covers delivery semantics, formats, size limit, and sibling routing. Only failure modes (missing path, oversize file, bad target) are unaddressed, which is a minor gap given the rich schema and annotations.

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 description coverage is 100%, so path, target, and caption are already fully documented in the schema. The description adds no parameter-level meaning (it never mentions target routing or the caption's two-message behavior), so 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?

States a specific verb and resource ('把本地图片以图片消息发到飞书会话') and explicitly contrasts with the sibling feishu_send_file for non-image files, so an agent can distinguish the two without opening either 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 a positive condition ('只在需要预览时用'), an explicit exclusion with the named alternative ('要发 PDF、压缩包、代码等非图片文件请用 feishu_send_file'), and concrete use cases (截图、图表、设计稿). The routing decision is fully specified.

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