Skip to main content
Glama
Fistacho

ha-nexus-agent

by Fistacho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Create a persistent notification

services_notify_persistent_create

Create or replace a persistent notification banner in the Home Assistant UI, with an optional title and stable notification_id to update or dismiss it later.

Instructions

Create or replace a persistent notification banner in the Home Assistant UI.

Calls persistent_notification.create with message, optional title and notification_id. Giving the same notification_id again replaces that notification's content in place; omitting it creates a new, separately addressable notification each time.

Use when: showing a UI banner that a person can dismiss, as opposed to a push notification. Not for: a push notification to a device — use services_send_notification. Returns: dict with notification_id and the raw service call result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoOptional notification title. Omit for no title.
messageYesNotification body text to show in the HA UI.
notification_idNoStable ID for later dismissal via services_notify_persistent_dismiss. Omit to create a new, unaddressable notification each call.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

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 show in the HA UI."
    • addedInput schema / properties / notification_id / description
      Added value: +"Stable ID for later dismissal via services_notify_persistent_dismiss. Omit to create a new, unaddressable notification each call."
    • addedInput schema / properties / title / description
      Added value: +"Optional notification title. Omit for no title."
  2. First observedv0.3.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare the safety profile (not read-only, not destructive, not idempotent), so the description needn't restate safety. It adds genuine behavior beyond them: giving the same notification_id replaces content in place, while omitting it creates a new separately addressable notification each call, plus the return shape. It stops short of detailing auth needs or dismissal interaction, but the replacement semantics are a meaningful addition.

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-loaded with the action and the crucial replacement behavior, then structured as Use when / Not for / Returns. Every sentence earns its place with no filler.

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

Completeness4/5

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

For a mutation tool with full annotation coverage and an existing output schema, the description is essentially complete: action, replacement semantics, usage routing and return mention are all present. The return detail is redundant given the output schema, but 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.

Parameters3/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 all three parameters including the notification_id replacement/dismissal behavior. The description largely restates the schema's own notification_id semantics rather than adding new syntax or format detail. Baseline 3 is appropriate when the schema carries the parameter semantics.

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 ('Create or replace a persistent notification banner in the Home Assistant UI') and even names the underlying service call. It distinguishes itself from the push-notification sibling by contrasting the dismissable UI banner against a device push, so an agent can tell it apart from services_send_notification without opening either schema.

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?

Explicitly provides 'Use when' (dismissable UI banner) and 'Not for' (push to a device), routing the agent to the named alternative services_send_notification. When-to-use and when-not-to-use are both stated, nothing left to inference.

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