Skip to main content
Glama

Alert Template Create

alert_template_create

Create a new LibreNMS alert template with a name, Blade template body, alert and recovery titles, and linked alert rule IDs for reusable alert messages.

Instructions

Create a new alert template in LibreNMS.

Input Schema

NameRequiredDescriptionDefault
payloadYesAlert template payload fields: - name (required): Template name - template (required): Template body (Laravel Blade syntax) - title (required): Alert title template - title_rec (required): Recovery title template - alert_rules (required): Array of alert rule IDs to associate with this template (use [] for none) LibreNMS renders title, title_rec and template against test data and reads alert_rules unconditionally, so all five fields must be present. Do not include template_id: LibreNMS would edit that template instead of creating one. Example: {"name": "Custom Alert", "template": "{{ $alert->title }}\nSeverity: {{ $alert->severity }}", "title": "Alert: {{ $alert->title }}", "title_rec": "Recovered: {{ $alert->title }}", "alert_rules": []}

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.12.0
    • changedInput schema / properties / payload / description
      Previous value: -"Alert template payload fields:\n- name (required): Template name\n- template (required): Template body (Laravel Blade syntax)\n- title (required): Alert title template\n- title_rec (required): Recovery title template\n- alert_rules (required): Array of alert rule IDs to associate with this template (use [] for none)\n\nLibreNMS renders title, title_rec and template against test data and reads\nalert_rules unconditionally, so all five fields must be present.\n\nExample:\n{\"name\": \"Custom Alert\", \"template\": \"{{ $alert->title }}\\nSeverity: {{ $alert->severity }}\", \"title\": \"Alert: {{ $alert->title }}\", \"title_rec\": \"Recovered: {{ $alert->title }}\", \"alert_rules\": []}"New value: +"Alert template payload fields:\n- name (required): Template name\n- template (required): Template body (Laravel Blade syntax)\n- title (required): Alert title template\n- title_rec (required): Recovery title template\n- alert_rules (required): Array of alert rule IDs to associate with this template (use [] for none)\n\nLibreNMS renders title, title_rec and template against test data and reads\nalert_rules unconditionally, so all five fields must be present. Do not\ninclude template_id: LibreNMS would edit that template instead of creating one.\n\nExample:\n{\"name\": \"Custom Alert\", \"template\": \"{{ $alert->title }}\\nSeverity: {{ $alert->severity }}\", \"title\": \"Alert: {{ $alert->title }}\", \"title_rec\": \"Recovered: {{ $alert->title }}\", \"alert_rules\": []}"
  2. Changed1 schema field changedv1.11.1
    • changedInput schema / properties / payload / description
      Previous value: -"Alert template payload fields:\n- name (required): Template name\n- template (required): Template body (Laravel Blade syntax)\n- title (optional): Alert title template\n- title_rec (optional): Recovery title template\n- rules (optional): Array of alert rule IDs to associate with this template\n\nExample:\n{\"name\": \"Custom Alert\", \"template\": \"{{ $alert->title }}\\nSeverity: {{ $alert->severity }}\", \"title\": \"Alert: {{ $alert->title }}\"}"New value: +"Alert template payload fields:\n- name (required): Template name\n- template (required): Template body (Laravel Blade syntax)\n- title (required): Alert title template\n- title_rec (required): Recovery title template\n- alert_rules (required): Array of alert rule IDs to associate with this template (use [] for none)\n\nLibreNMS renders title, title_rec and template against test data and reads\nalert_rules unconditionally, so all five fields must be present.\n\nExample:\n{\"name\": \"Custom Alert\", \"template\": \"{{ $alert->title }}\\nSeverity: {{ $alert->severity }}\", \"title\": \"Alert: {{ $alert->title }}\", \"title_rec\": \"Recovered: {{ $alert->title }}\", \"alert_rules\": []}"
  3. First observedv1.9.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, and the description adds nothing beyond them. It does not warn that repeated calls create duplicate templates (the non-idempotent consequence), nor note any permission requirements. The valuable behavioral notes (test-data rendering, omitting template_id) live in the schema, not the description.

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?

A single front-loaded sentence with zero filler, which is efficient. It is arguably too terse for a mutation tool, but nothing in it is wasted.

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?

An output schema exists, so return values need not be explained, and the schema itself carries rich field-level detail. However, for a create/mutation operation the description omits routing guidance versus alert_template_edit and any idempotency warning, leaving a visible gap.

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%, so the baseline is 3. The single 'payload' parameter is exhaustively documented in the schema, including required fields, an example, and the template_id gotcha; the description adds no additional parameter meaning.

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?

States a specific verb ('Create') and resource ('alert template') with the target system (LibreNMS), so the operation is unambiguous. It does not, however, differentiate itself in text from siblings like alert_template_edit or alert_template_get, relying on the name alone.

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 offers no when-to-use guidance, no prerequisites, and no mention of the sibling alert_template_edit for modifying existing templates. An agent must infer the create-vs-edit boundary purely from the tool name.

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