Skip to main content
Glama

Send to HomeAssistant Mobile APP

ha_send_mobile

Send notifications to Home Assistant Mobile app with customizable message, title, subtitle, and optional extended data including images, videos, and action buttons.

Instructions

Send a notification to Home Assistant Mobile APP

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYesNotification content
titleNoNotification title
subtitleNoNotification subtitle
dataNoExtended data, json string. ```json { "image": "http://a.com/photo.jpg", "video": "http://a.com/video.mp4", "audio": "http://a.com/audio.mp3", # ios only "actions": [ { "action": "YOUR_ACTION_KEY", # Required. The identifier passed back in events. "title": "Do Something", "icon": "sfsymbols:bell.slash" # ios only }, { "action": "URL", # Must be set to URI if you plan to use a URI "title": "Open Url", # The action button title "url": "https://github.com" # URL to open when action is selected }, { "action": "REPLY", # When set to REPLY, you will be prompted for text to send with the event. "title": "Reply me", "behavior": "textInput" # Optional. Set to `textInput` to prompt for text to return with the event. This also occurs when setting the action to `REPLY`. } ] } ``` All fields in the extended data are optional. {}
urlNoOpening a URL when tapping on a notification
device_keyNoDevice key, Default to get from environment variables

Implementation Reference

  • The actual handler function that sends notifications to Home Assistant Mobile APP. It constructs the request with authentication, resolves the device key, formats extended data (image, video, audio, actions, URL, subtitle), and POSTs to the Home Assistant notify service.
    def ha_send_mobile(
        message: str = Field(description="Notification content"),
        title: str = Field("", description="Notification title"),
        subtitle: str = Field("", description="Notification subtitle"),
        data: str | dict = Field("{}", description=f"Extended data, json string.{HA_NOTIFY_DATA_PROMPT}"),
        url: str = Field("", description="Opening a URL when tapping on a notification"),
        device_key: str = Field("", description="Device key, Default to get from environment variables"),
    ):
        base = os.getenv("HASS_BASE_URL") or "http://homeassistant.local:8123"
        if not (token := os.getenv("HASS_ACCESS_TOKEN")):
            return "You need to set `HASS_ACCESS_TOKEN` in the environment variable"
    
        headers = {"Authorization": f"Bearer {token}"}
        if not device_key:
            device_key = os.getenv("HASS_MOBILE_KEY", "")
        if not device_key:
            res = requests.get(f"{base}/api/services", headers=headers)
            for service in res.json() or []:
                if service["domain"] != "notify":
                    continue
                for name in service["services"]:
                    if name.startswith("mobile_app_"):
                        device_key = name
                        break
        if device_key.startswith("notify."):
            device_key = device_key[7:]
        elif not device_key.startswith("mobile_app_"):
            device_key = f"mobile_app_{device_key}"
    
        if isinstance(data, str):
            try:
                data = json.loads(data)
            except ValueError:
                data = {}
        elif not isinstance(data, dict):
            data = {}
        if url:
            data.setdefault("url", url)  # ios
            data.setdefault("clickAction", url)  # android
        if subtitle:
            data.setdefault("subtitle", subtitle)  # ios
            data.setdefault("subject", subtitle)  # android
    
        res = requests.post(
            f"{base}/api/services/notify/{device_key}",
            json={
                "message": message,
                "title": title,
                "data": data,
            },
            headers=headers,
        )
        return res.json()
  • The function signature acts as the schema definition. Parameters: message (str, required), title (str, default ''), subtitle (str, default ''), data (str|dict, default '{}'), url (str, default ''), device_key (str, default ''). All use pydantic Field for descriptions.
    def ha_send_mobile(
        message: str = Field(description="Notification content"),
        title: str = Field("", description="Notification title"),
        subtitle: str = Field("", description="Notification subtitle"),
        data: str | dict = Field("{}", description=f"Extended data, json string.{HA_NOTIFY_DATA_PROMPT}"),
        url: str = Field("", description="Opening a URL when tapping on a notification"),
        device_key: str = Field("", description="Device key, Default to get from environment variables"),
    ):
  • The registration of the tool via the @mcp.tool decorator, called from the add_tools(mcp) function which is invoked in __init__.py line 22.
    def add_tools(mcp: FastMCP, logger=None):
    
        @mcp.tool(
            title="Send to HomeAssistant Mobile APP",
            description="Send a notification to Home Assistant Mobile APP",
        )
  • HA_NOTIFY_DATA_PROMPT constant provides documentation for the extended data JSON schema, showing supported fields: image, video, audio, actions (with action/title/icon/url/behavior).
    HA_NOTIFY_DATA_PROMPT = """
    ```json
    {
      "image": "http://a.com/photo.jpg",
      "video": "http://a.com/video.mp4",
      "audio": "http://a.com/audio.mp3", # ios only
      "actions": [
        {
          "action": "YOUR_ACTION_KEY", # Required. The identifier passed back in events.
          "title": "Do Something",
          "icon": "sfsymbols:bell.slash" # ios only
        },
        {
          "action": "URL", # Must be set to URI if you plan to use a URI
          "title": "Open Url", # The action button title
          "url": "https://github.com" # URL to open when action is selected
        },
        {
          "action": "REPLY", # When set to REPLY, you will be prompted for text to send with the event.
          "title": "Reply me",
          "behavior": "textInput" # Optional. Set to `textInput` to prompt for text to return with the event. This also occurs when setting the action to `REPLY`.
        }
      ]
    }
    ```
    All fields in the extended data are optional.
    """
Behavior2/5

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

No annotations provided. The description gives no information about behavior such as whether the notification is sent synchronously, error handling, authentication needs, or rate limits. The description solely describes the action.

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?

Single sentence is concise and front-loaded with the core purpose. No unnecessary words, though it could be slightly expanded with brief context.

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?

Input schema fully covers parameters. No output schema exists, but description doesn't mention expected return value. Lacks guidance on selection among siblings. Adequate for a simple notification tool but not comprehensive.

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% with detailed documentation for all parameters, including a JSON example for 'data'. The description itself adds no extra parameter meaning beyond what's in the schema, so baseline 3 is appropriate.

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 'Send a notification to Home Assistant Mobile APP' clearly states the action and target. The name and title reinforce this. Sibling tools are various other notification services, making the purpose distinct and specific.

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 the many sibling notification tools. No mention of prerequisites, environment setup, or device registration.

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