Skip to main content
Glama
al-one

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

Ntfy Push Notification

ntfy_send_notify

Send notifications via Ntfy to multiple platforms including Weixin, Telegram, Bark, and Lark with customizable messages, priorities, and actions.

Instructions

Push a notification via Ntfy

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYesNotification message body; set to `triggered` if empty or not passed
titleNoNotification title
topicNoTarget topic name or URL
clickNoURL opened when notification is clicked
attachNoURL of an attachment
iconNoURL of notification icon
markdownNoSet to `true` if the message is Markdown-formatted
filenameNoFile name of the attachment
priorityNoMessage priority with 1=min, 3=default and 5=max
delayNoTimestamp or duration for delayed delivery. Example: 30min, 9am
actionsNoList of action buttons. The following actions are supported: - view: Opens a website or app when the action button is tapped - broadcast: Sends an Android broadcast intent when the action button is tapped (only supported on Android) - http: Sends HTTP POST/GET/PUT request when the action button is tapped ```json [ { "action": "view", "label": "Open portal", "url": "https://home.nest.com/", "clear": true }, { "action": "http", "label": "Turn down", "url": "https://api.nest.com/", "body": "{"temperature": 65}" }, { "action": "broadcast", "label": "Take picture", "extras": { "cmd": "pic", "camera": "front" } } ] ```

Implementation Reference

  • Registers the ntfy_send_notify tool with FastMCP using the @mcp.tool decorator.
    @mcp.tool(
        title="Ntfy Push Notification",
        description="Push a notification via Ntfy",
    )
  • The handler function implementing the ntfy_send_notify tool logic, including input schema definitions via Pydantic Field and the HTTP POST request to the Ntfy service.
    def ntfy_send_notify(
        message: str = Field(description="Notification message body; set to `triggered` if empty or not passed"),
        title: str = Field("", description="Notification title"),
        topic: str = Field("", description="Target topic name or URL"),
        click: str = Field("", description="URL opened when notification is clicked"),
        attach: str = Field("", description="URL of an attachment"),
        icon: str = Field("", description="URL of notification icon"),
        markdown: bool = Field(False, description="Set to `true` if the message is Markdown-formatted"),
        filename: str = Field("", description="File name of the attachment"),
        priority: int = Field(3, description="Message priority with 1=min, 3=default and 5=max"),
        delay: str = Field("", description="Timestamp or duration for delayed delivery. Example: 30min, 9am"),
        actions: list | None = Field(None, description=f"List of action buttons.{NTFY_ACTIONS_RULE}"),
    ):
        """
        https://docs.ntfy.sh/publish/#publish-as-json
        """
        base = os.getenv("NTFY_BASE_URL") or "https://ntfy.sh"
        if topic and topic.startswith("http"):
            base, topic = topic.rsplit("/", 1)
        if not topic:
            topic = os.getenv("NTFY_DEFAULT_TOPIC", "")
        data = {
            "topic": topic,
            "title": title,
            "message": message,
            "click": click,
            "icon": icon,
            "markdown": markdown or False,
            "priority": priority,
            "delay": delay,
        }
        if attach:
            data["attach"] = attach
            data["filename"] = filename
        if actions:
            data["actions"] = actions
        res = requests.post(f"{base}", json=data)
        return res.json()
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Push a notification' implies a write operation that sends data externally, but the description doesn't mention authentication requirements, rate limits, error conditions, or what happens when the notification is delivered. For a tool with 11 parameters and no 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 sentence with zero wasted words. It's perfectly front-loaded with the core action and immediately communicates the tool's purpose without unnecessary elaboration.

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 complex notification tool with 11 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what Ntfy is, what platforms it supports, what the response looks like, or any behavioral characteristics. The agent would need to rely entirely on the input schema without contextual understanding of the service.

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 11 parameters thoroughly with descriptions, defaults, and examples. The description adds no parameter information beyond what's in the schema, meeting the baseline expectation but not providing additional value.

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 ('Push') and resource ('notification via Ntfy'), making the purpose immediately understandable. However, it doesn't differentiate this Ntfy-based notification tool from the many sibling notification tools (e.g., bark_send_notify, tg_send_message), which would be required for a score of 5.

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 specific tool versus the many sibling notification alternatives. There's no mention of Ntfy's unique features, target platforms, or any context that would help an agent choose this over other notification tools in the server.

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