Skip to main content
Glama

send_notification

Deliver markdown messages to all configured channels—Feishu, DingTalk, Slack, Telegram, email—with automatic format adaptation per platform.

Instructions

向已配置的通知渠道发送消息

接受 markdown 格式内容,内部自动适配各渠道的格式要求和限制:

  • 飞书:Markdown 卡片消息(支持 粗体彩色文本、链接、---)

  • 钉钉:Markdown(自动降级标题为 ###、剥离 标签和删除线)

  • 企业微信:Markdown(自动剥离 # 标题、---、 标签、删除线)

  • Telegram:HTML(自动转换 **→、*→、~~→、>→

  • Email:HTML 邮件(完整网页样式,支持 # 标题、---、粗体斜体)

  • ntfy:Markdown(自动剥离 标签)

  • Bark:Markdown(自动简化为粗体+链接,适配 iOS 推送)

  • Slack:mrkdwn(自动转换 **→*、~~→~、text→<url|text>)

  • 通用 Webhook:Markdown(支持自定义模板)

提示:发送前可调用 get_channel_format_guide 获取目标渠道的详细格式化策略, 以生成最佳排版效果的消息内容。

Args: message: markdown 格式的消息内容(必需) title: 消息标题,默认 "TrendRadar 通知" channels: 指定发送的渠道列表,不指定则发送到所有已配置渠道 可选值: feishu, dingtalk, wework, telegram, email, ntfy, bark, slack, generic_webhook

Returns: JSON格式的发送结果,包含每个渠道的发送状态

Examples: - send_notification(message="测试消息\n这是一条测试通知") - send_notification(message="紧急通知", title="系统告警", channels=["feishu", "dingtalk"])

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoTrendRadar 通知
messageYes
channelsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations provided, the description carries the full behavioral disclosure burden and does so thoroughly. It explains internal adaptation per channel, exact Markdown-to-HTML/mrkdwn transformations, default behavior of sending to all channels when none are specified, default title, and the JSON result containing per-channel status. This gives the agent a strong model of side effects and return behavior.

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 description is well structured with purpose, per-channel details, arguments, return type, and examples. It is somewhat long, but the length is largely justified by the complexity of eight different channel formatting behaviors. The Args section partially duplicates schema defaults, but it adds necessary semantic value given zero schema descriptions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is complete enough for an agent to invoke the tool correctly: it specifies required vs optional parameters, accepted channel values, default behavior, output shape, and even an example for common calls. The existence of an output schema further covers return structure, and the pointer to get_channel_format_guide fills the formatting-optimization gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must fully compensate, and it does. It defines message as Markdown content, title with its default value, and channels with the full list of allowed values plus the default of sending to all configured channels. This adds far more meaning than the bare schema types and defaults.

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?

The description opens with a clear statement of purpose: '向已配置的通知渠道发送消息' — sends messages to configured notification channels. It gives the specific verb and resource, and the detailed channel list distinguishes it from sibling read/analysis tools, none of which send notifications.

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

Usage Guidelines4/5

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

The description clearly indicates when to use the tool: whenever a notification needs to be sent to one or more configured channels. It also points the agent to get_channel_format_guide for detailed formatting strategy before sending. There are no explicitly stated exclusions, but no sibling tool offers an alternative sending path, so exclusions are less necessary.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/17191004/TrendRadar_260829'

If you have feedback or need assistance with the MCP directory API, please join our Discord server