Skip to main content
Glama
17191004

TrendRadar MCP Server

by 17191004

send_notification

Send markdown-formatted notifications to multiple channels like Feishu, DingTalk, Telegram, and email, with automatic formatting conversion for each platform. Specify message, title, and target channels.

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
Behavior4/5

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

No annotations are provided, so the description carries the transparency burden. It discloses useful behavior such as auto-adapting Markdown per channel, defaulting to all configured channels when none are specified, and returning JSON with per-channel send status. It doesn't discuss irreversibility, retry, or failure behavior, but the key behavioral traits are explained.

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?

The description is well-structured and front-loaded: purpose first, then channel-specific formatting details, a usage tip, structured Args/Returns, and representative examples. The length is justified because the channel-by-channel formatting behavior is genuinely useful to an agent.

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?

Given the output schema can handle return-type details, the description is complete enough for reliable tool selection and invocation. It covers the exact parameters, per-channel behavior, channel options, default behavior, and a companion helper tool, so an agent has enough context to call it correctly.

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?

With 0% schema description coverage, the description compensates well: message must be Markdown, title has a default value, and channels lists all supported target channels plus the critical semantic that omitting it means 'all configured channels'. The example calls also clarify realistic usage.

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 clearly states the action: send a message to configured notification channels ('向已配置的通知渠道发送消息'), then explains the Markdown input and per-channel adaptation. This distinguishes it from sibling read/search/report tools such as get_latest_news and generate_summary_report.

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?

It gives concrete usage context: use this tool to send notifications, and before sending it suggests calling get_channel_format_guide for detailed formatting policy. It could more explicitly state when not to use it or name excluding conditions, but the send-vs-read distinction is effectively clear.

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'

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