Skip to main content
Glama

alert_template_create

Create a new alert template in LibreNMS to define custom notification titles, bodies, recovery messages, and associated alert rules.

Instructions

Create a new alert template in LibreNMS.

Input Schema

TableJSON 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. Example: {"name": "Custom Alert", "template": "{{ $alert->title }}\nSeverity: {{ $alert->severity }}", "title": "Alert: {{ $alert->title }}", "title_rec": "Recovered: {{ $alert->title }}", "alert_rules": []}

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

The description text adds no behavioral detail beyond what annotations already imply (write operation, non-idempotent, non-destructive). It does not mention validation behavior, duplicate handling, permission requirements, or side effects. While the payload schema describes validation, that is a structured field and not credited here. The description is consistent with annotations but provides no extra transparency.

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?

The description is a single, concise sentence that immediately states the verb and object. It contains no filler or redundant information. It is well-structured and front-loaded for quick parsing.

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?

The tool has a complex nested parameter but the schema and output schema cover most details. However, the description lacks usage guidance and behavioral nuances, making it incomplete when considered alone. For an agent selecting among CRUD siblings, the absence of usage context is a notable 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?

The input schema has 100% description coverage for the only parameter, including all five required fields, an example, and validation notes. Since the schema already does the heavy lifting, the description text adds no additional parameter meaning. The baseline of 3 is appropriate.

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 clearly states a specific action ('Create') on a specific resource ('alert template') in a specific system ('LibreNMS'). The use of 'new' distinguishes it from alert_template_edit and alert_template_get. However, it lacks any scope or qualifier that would further differentiate it from alternatives, so it doesn't earn the top score.

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?

No guidance is provided on when to use this tool versus alternatives like alert_template_edit. The description simply states what it does, not whether to prefer it over editing or under what circumstances (e.g., creating a new template vs. modifying an existing one). The rich payload schema mentions required fields but not usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mhajder/librenms-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server