Skip to main content
Glama
al-one

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

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

wework_send_news

Send rich media notifications with titles, links, and images to WeChat Work group chats via bot integration for team communication updates.

Instructions

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

Input Schema

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

Implementation Reference

  • The handler function that implements the logic for sending a single news article (title, description, url, picurl) via WeWork group robot webhook using POST request to the API.
    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 @mcp.tool decorator registers the wework_send_news function as an MCP tool with specified title and description.
    @mcp.tool(
        title="企业微信群机器人-发送图文消息",
        description="通过企业微信群机器人发送图文链接消息",
    )
  • Initialization of the main FastMCP instance and calls to add_tools from modules, including wework.add_tools(mcp), which registers the wework_send_news tool.
    mcp = FastMCP(name="mcp-notify", version="0.1.8")
    wework.add_tools(mcp)
    tgbot.add_tools(mcp)
    other.add_tools(mcp)
    hass.add_tools(mcp)
    util.add_tools(mcp)
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While '发送' (send) implies a write operation, the description doesn't disclose any behavioral traits: no information about authentication requirements (beyond the bot_key parameter), rate limits, error conditions, whether messages are ephemeral or persistent, or what happens on success/failure. For a messaging tool with zero annotation coverage, this is a significant gap.

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 a single, efficient Chinese sentence that directly states the tool's purpose without any fluff. It's appropriately sized for a straightforward messaging tool and front-loads the essential information. Every word earns its place.

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

Completeness2/5

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

For a messaging tool with no annotations and no output schema, the description is incomplete. It doesn't explain what constitutes success or failure, what the response looks like (if any), or any side effects. While the purpose is clear, the behavioral context needed for reliable tool invocation is missing. The description should address authentication, error handling, and response format given the lack of structured metadata.

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 the schema already documents all 5 parameters thoroughly. The description doesn't add any parameter semantics beyond what's in the schema - it doesn't explain relationships between parameters (e.g., how title, url, picurl, and description combine to form the 'graphic link message'), nor does it provide examples of valid parameter combinations. Baseline 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('发送图文链接消息' - send graphic link message) and resource ('通过企业微信群机器人' - via WeWork group robot). It specifies the message type as 'graphic link message', which distinguishes it from sibling tools like wework_send_text and wework_send_image. However, it doesn't explicitly differentiate from wework_app_send_news, which appears to be a similar app-based tool.

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?

The description provides no guidance on when to use this tool versus alternatives. With multiple WeWork messaging tools available (wework_send_text, wework_send_image, wework_app_send_news, etc.), there's no indication of when this specific 'graphic link message' format is appropriate versus plain text, images, or app-based news messages. No prerequisites or exclusions are mentioned.

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