Skip to main content
Glama
al-one

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

PushPlus推送消息

pushplus_send_msg

Send notifications via PushPlus to multiple platforms including WeChat, Telegram, Bark, and Lark. Configure message content, title, format, and delivery channel for cross-platform alerts.

Instructions

通过PushPlus(推送加)推送消息

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYes消息内容
titleNo消息标题
tokenNo用户token,默认从环境变量获取
templateNo消息内容格式: `html`(默认)/`txt`/`markdown`
channelNo发送渠道: `wechat`(默认)/`webhook`/`mail`

Implementation Reference

  • The handler function that executes the 'pushplus_send_msg' tool logic, sending a POST request to PushPlus API with configurable parameters.
    def pushplus_send_msg(
        content: str = Field(description="消息内容"),
        title: str = Field("", description="消息标题"),
        token: str = Field("", description="用户token,默认从环境变量获取"),
        template: str = Field("", description="消息内容格式: `html`(默认)/`txt`/`markdown`"),
        channel: str = Field("", description="发送渠道: `wechat`(默认)/`webhook`/`mail`"),
    ):
        """
        https://www.pushplus.plus/doc/guide/api.html
        """
        if not token:
            token = os.getenv("PUSH_PLUS_TOKEN", "")
        base = os.getenv("PUSH_PLUS_BASE_URL") or "http://www.pushplus.plus"
        res = requests.post(
            f"{base}/{token}",
            json={
                "content": content,
                "title": title,
                "template": template,
                "channel": channel,
            },
        )
        return res.json()
  • Pydantic Field-based input schema defining parameters for the 'pushplus_send_msg' tool.
        content: str = Field(description="消息内容"),
        title: str = Field("", description="消息标题"),
        token: str = Field("", description="用户token,默认从环境变量获取"),
        template: str = Field("", description="消息内容格式: `html`(默认)/`txt`/`markdown`"),
        channel: str = Field("", description="发送渠道: `wechat`(默认)/`webhook`/`mail`"),
    ):
  • Registers the 'pushplus_send_msg' tool using FastMCP's @mcp.tool decorator with title and description.
    @mcp.tool(
        title="PushPlus推送消息",
        description="通过PushPlus(推送加)推送消息",
    )
  • Calls add_tools on the 'other' module to register all its tools, including 'pushplus_send_msg', to the main MCP instance.
    other.add_tools(mcp)
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. The description only states that it '推送消息' (sends/pushes messages) but doesn't disclose any behavioral traits: no information about authentication requirements (though the schema mentions token from environment variables), no rate limits, no error handling, no delivery guarantees, no mention of what happens if the service is unavailable. For a message sending tool with zero annotation coverage, this is inadequate.

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 extremely concise - a single Chinese phrase that directly states the tool's function. There's zero wasted language or unnecessary elaboration. While it's arguably too brief for proper documentation, it earns full marks for conciseness as every word serves the core purpose of identifying the tool.

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?

Given the complexity of a message sending tool with 5 parameters, no annotations, and no output schema, the description is severely incomplete. It doesn't explain what PushPlus is, what types of messages it supports, what the response looks like, or any behavioral characteristics. The agent would need to rely entirely on the input schema and guesswork about the service behavior.

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?

The schema description coverage is 100%, so the schema already documents all 5 parameters thoroughly with descriptions, defaults, and required status. The description adds absolutely no additional parameter information beyond what's in the schema. According to the scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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

Purpose2/5

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

The description '通过PushPlus(推送加)推送消息' is a tautology that essentially restates the tool name 'pushplus_send_msg' in Chinese. It specifies the service (PushPlus) and the action (推送消息/send message), but doesn't clarify what type of messages or to what endpoints. While it distinguishes from siblings by mentioning PushPlus specifically, it lacks the specificity of verb+resource that would make it truly clear.

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 the many sibling notification tools (Bark, DingTalk, Lark, Telegram, WeWork, etc.). It doesn't mention any specific use cases for PushPlus, nor does it provide any context about when this service would be preferred over alternatives. The agent receives no help in selecting between these similar notification tools.

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