Skip to main content
Glama
al-one

MCP Server for notify to weixin / telegram / bark / lark

企业微信群机器人-发送图文消息

wework_send_news

Send rich news links with title, URL, and optional description/image to WeChat Work group bot.

Instructions

通过企业微信群机器人发送图文链接消息

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes标题,不超过128个字节
urlYes跳转链接,必填
picurlNo图片URL
descriptionNo描述,不超过512个字节
bot_keyNo企业微信群机器人key,uuid格式,默认从环境变量获取

Implementation Reference

  • The actual implementation of the 'wework_send_news' tool. It sends a news/article message (title, url, picurl, description) via the WeWork group bot webhook API. Registered as an MCP tool via the @mcp.tool decorator within the add_tools() function.
    @mcp.tool(
        title="企业微信群机器人-发送图文消息",
        description="通过企业微信群机器人发送图文链接消息",
    )
    def wework_send_news(
        title: str = Field(description="标题,不超过128个字节"),
        url: str = Field(description="跳转链接,必填"),
        picurl: str = Field("", description="图片URL"),
        description: str = Field("", description="描述,不超过512个字节"),
        bot_key: str = FIELD_BOT_KEY,
    ):
        res = requests.post(
            f"{WEWORK_BASE_URL}/cgi-bin/webhook/send?key={bot_key or WEWORK_BOT_KEY}",
            json={
                "msgtype": "news",
                "news": {
                    "articles": [
                        {
                            "title": title,
                            "description": description,
                            "url": url,
                            "picurl": picurl,
                        },
                    ],
                },
            },
        )
        return res.json()
  • The 'add_tools' function that registers all WeWork tools onto the FastMCP server. The 'wework_send_news' tool is defined (lines 61-88) inside this function and decorated with @mcp.tool.
    def add_tools(mcp: FastMCP, logger=None):
  • The MCP server initialization file calls 'wework.add_tools(mcp)' on line 19 to register all WeWork tools including wework_send_news.
    wework.add_tools(mcp)
Behavior2/5

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

No annotations provided; description does not disclose behavioral traits such as side effects, authorization requirements, rate limits, or whether the message is immediately sent. The single verb 'send' implies a write operation but offers no further transparency.

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?

One clear sentence, no redundancy, efficiently communicates the core function. Could be slightly more structured but is appropriately terse.

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

Completeness3/5

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

For a simple tool with 5 straightforward parameters and no output schema, the description provides the essential action but lacks usage context, alternatives, and behavioral notes. Not fully complete but minimally adequate.

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?

Input schema has 100% description coverage for all 5 parameters, so schema already clarifies meaning. Description adds no additional context beyond listing the resource type.

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) and resource (image-text link message) and specifies the channel (enterprise WeChat group robot), distinguishing it from siblings like wework_send_text and wework_send_image.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternative wework tools (e.g., wework_send_text, wework_send_image). The description lacks any context about prerequisites or alternatives.

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/al-one/mcp-notify'

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