Skip to main content
Glama

Send a notification

services_send_notification

Send push notifications to a person or device through a Home Assistant notify service. Specify a message, optional title, and target channel.

Instructions

Send a notification through a Home Assistant notify service.

Calls notify.<target> (or plain notify.notify when target is omitted) with message and optional title; target may include the domain (notify.xyz) or be a bare service name, but a dotted target must name the notify domain itself (ADR-0006 D6) — otherwise it would let any domain.service be reached under cover of a "notification". Each call dispatches a new notification to whatever device or channel that service delivers to, which can be outside the local network (e.g. a phone push).

Use when: pushing a message to a person or device through a configured notify service. Not for: an in-UI banner tracked by an ID — use services_notify_persistent_create. Returns: the list of states changed by the call (notify services typically change none). Errors: {"error": "invalid_notify_target", "message": ...} when a dotted target names a domain other than notify; {"error": "invalid_service_name"} when the part after notify. is not itself a bare [A-Za-z0-9_]+ service name (e.g. a second dot).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoOptional notification title. Omit for no title.
targetNoNotify service to use, e.g. 'mobile_app_phone' or 'notify.mobile_app_phone'. Omit to use the default 'notify' service.
messageYesNotification body text to deliver.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.25.1
    • addedInput schema / properties / message / description
      Added value: +"Notification body text to deliver."
    • addedInput schema / properties / target / description
      Added value: +"Notify service to use, e.g. 'mobile_app_phone' or 'notify.mobile_app_phone'. Omit to use the default 'notify' service."
    • addedInput schema / properties / title / description
      Added value: +"Optional notification title. Omit for no title."
  2. First observedv0.3.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and idempotentHint=false, but the description adds substantially more: each call dispatches a new notification, it can reach outside the local network (phone push), the ADR-0006 D6 dotted-target constraint, the return value (list of changed states), and concrete error shapes/invalid_notify_target. This is rich context beyond structured fields.

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?

Front-loads what the tool does, then cleanly segments Use when / Not for / Returns / Errors. The description is long but every section carries distinct, actionable information; no filler.

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

Completeness5/5

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

For a non-idempotent, open-world dispatch tool with an output schema, the description covers target resolution rules, side effects, return shape, and failure modes. Nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% so the schema already documents message/title/target, but the description adds a non-obvious constraint absent from the schema: a dotted `target` must name the `notify` domain and the part after `notify.` must be a bare service name. This meaningfully extends the parameter contract beyond the field descriptions.

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?

States a specific verb and resource ('Send a notification through a Home Assistant notify service') and specifies exactly what it calls (`notify.<target>` or `notify.notify`). It distinguishes itself from sibling services_notify_persistent_create by explaining that it dispatches to a device/channel rather than an in-UI banner.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit 'Use when: pushing a message to a person or device through a configured notify service' and 'Not for: an in-UI banner tracked by an ID — use services_notify_persistent_create.' It names the alternative and the condition that selects it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools