Skip to main content
Glama

notification_add

Adds a Loxone app push/message notification and wires a source to a page so the specified text is sent on the source signal's rising edge.

Instructions

Adds a Loxone notification (push/message in the Loxone app) and wires 'source' to it on 'page'. 'text' is the message sent on a rising edge of 'source'.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "<title>",
      "text": "<text>",
      "source": "<source>",
      "page": "<page>"
    },
    "name": "notification_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYes
textYes
titleYes
sourceYes
source_keyNo
min_time_msNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one genuinely useful trait: the message is sent on a rising edge of 'source', which tells the agent this is an edge-triggered, persistent notification rather than a one-off send. However, it says nothing about throttling/debounce (implicitly the unexplained min_time_ms default of 5000), duplicate registration, persistence across rebuilds, or required permissions.

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?

Two short sentences that front-load the action and then add the key trigger semantics, with no filler. The quoted field references make the second sentence slightly dense but still readable.

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 six-parameter mutation tool with no annotations and no output schema, the description covers only the core wiring concept. The agent still lacks information on min_time_ms behavior, source_key purpose, and what happens on repeated calls or whether the notification survives a project build.

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 0%, so the description must compensate, and it does explain the two least obvious parameters: 'source' (the trigger wired to the notification) and 'page' (the wiring target), plus 'text'. It leaves 'source_key' and 'min_time_ms' completely undefined in both schema and description, and 'title' only implicitly as the notification name.

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 opens with a specific verb and resource ('Adds a Loxone notification') and names the concrete side effect of wiring 'source' to it on 'page'. It is distinct from structural siblings like block_add or page_add, though it does not explicitly contrast itself with them.

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?

There is no when-to-use or when-not-to-use guidance, no prerequisites (e.g. whether a page must already exist or a project must be open), and no mention of alternatives among the many *_add siblings. Usage can only be inferred from the wiring explanation.

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