librenms-mcp

Overview Schema Source Related Servers Discussions Admin

Alert Template Edit

alert_template_edit

DestructiveIdempotent

Edit an existing LibreNMS alert template by sending complete template details, including the required template ID, body, titles, and alert rule associations.

Instructions

Edit an existing alert template in LibreNMS.

Input Schema

Name	Required	Description	Default
`payload`	Yes	Alert template edit payload (must include template_id): - template_id (required): Integer template ID to edit. Without it LibreNMS would create a new template, so the tool refuses the call. - 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 replaces the whole template on edit, so resend every field, not just the ones being changed.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.12.0Oct 15, 2026

changedInput schema / properties / payload / description

Previous value: -"Alert template edit payload (must include template_id):\n- template_id (required): Template ID to edit. Without it LibreNMS creates a new\n  template instead of editing the existing one.\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 replaces the whole template on edit, so resend every field, not just\nthe ones being changed."New value: +"Alert template edit payload (must include template_id):\n- template_id (required): Integer template ID to edit. Without it LibreNMS would create a\n  new template, so the tool refuses the call.\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 replaces the whole template on edit, so resend every field, not just\nthe ones being changed."

Changed1 schema field changedv1.11.1Aug 14, 2026

changedInput schema / properties / payload / description

Previous value: -"Alert template edit payload (must include id field):\n- id (required): Template ID to edit\n- name: Template name\n- template: Template body (Laravel Blade syntax)\n- title: Alert title template\n- title_rec: Recovery title template\n- rules: Array of alert rule IDs to associate with this template"New value: +"Alert template edit payload (must include template_id):\n- template_id (required): Template ID to edit. Without it LibreNMS creates a new\n  template instead of editing the existing one.\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 replaces the whole template on edit, so resend every field, not just\nthe ones being changed."

First observedv1.9.0May 27, 2026

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=true, and destructiveHint=true, covering the safety profile. The description itself adds nothing beyond that — it does not mention the full-template-replacement behavior or the refusal when template_id is missing (those details live only in the schema).

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 short, front-loaded sentence with no waste. It is efficient, though its brevity borders on under-specification rather than true conciseness.

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 described, and the schema documents destructive replacement semantics. However, for a destructive mutation the description contributes essentially nothing on its own, leaving it minimally adequate.

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% and the single nested payload object is thoroughly documented with all required fields. The description adds no parameter detail of its own, so the baseline 3 applies since the schema does all the heavy lifting.

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 ("Edit") and resource ("alert template") scoped to "existing" templates in LibreNMS. The word "existing" implicitly distinguishes it from the sibling alert_template_create, though it does not name the sibling explicitly.

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 gives no guidance on when to use this tool versus alert_template_create or alert_template_get. There is no mention of prerequisites (e.g., that the template must already exist) or conditions that would select an alternative.

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

Deploy Server