Skip to main content
Glama

PushPlus推送消息

pushplus_send_msg

Send push notifications through PushPlus to WeChat, webhook, or email. Customize message title, format, and delivery channel.

Instructions

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

Input Schema

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

Implementation Reference

  • Tool registered by calling other.add_tools(mcp), which registers pushplus_send_msg as an MCP tool.
    other.add_tools(mcp)
    hass.add_tools(mcp)
    util.add_tools(mcp)
  • Handler function for pushplus_send_msg: sends a message via PushPlus API using content, title, token, template, and channel 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()
  • MCP tool registration decorator for pushplus_send_msg with title 'PushPlus推送消息' and description.
    @mcp.tool(
        title="PushPlus推送消息",
        description="通过PushPlus(推送加)推送消息",
    )
  • Input parameters defined with Pydantic Field: content (required), title, token, template, channel (all optional with defaults).
    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`"),
Behavior2/5

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

No annotations present, so description carries full burden. It only states 'push message' without disclosing authentication needs, rate limits, or error 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?

One sentence directly stating purpose, no unnecessary words. Could be more informative but not verbose.

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?

No output schema and no annotations. The description lacks details on return values, error handling, or constraints. Given the complexity of siblings, more context is needed.

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. The description adds no additional parameter meaning beyond the schema, so baseline of 3.

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 verb (push) and resource (messages via PushPlus). However, it does not differentiate from sibling notification tools like bark_send_notify or ding_send_text.

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 alternatives. No when-to-use or when-not-to-use context provided.

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

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